Disclaimer
Sprngy Platform Documentation Guide
Release 2.0.0
Copyright © Sprngy Corporation. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
This document is intended for:
SPRNGY Administrators
SPRNGY Developers
SPRNGY Architects
This document is a walkthrough to create Module and Entities through the Sprngy UI.
Setting up an Application
Here click on ‘Create New Module’ button.
On Click, above screen will be rendered, It takes in Module Name, Entity names list.
On clicking NEXT, you can setup the parent child relationship among the entities if exist. Once done, click on SUBMIT button.
NOTE: Provide parent entity name(s) in the screen only if the entities are related. If not, leave the ‘Parent’ field blank.
It is important that the entities names are not same as hive reserved keywords.
After submitting, there will be a popup window with a list of given entity and parent relations for verification. Once verified click on YES to create the application.
Editing an Application
For editing, go to Application Configuration from the menu and select the module name you want to edit from the dropdown and click 'SUBMIT'. This will display the existing entity relation it has.
After making the required changes click on submit, which would bring up a popup to verify the changes made. If the changes are correct click on ‘YES’ button, which would update the parent- child relationship of that model, create new entities if added and create a new library with the changes.
It is important to note that entity names should not be edited if models (meta/ingest etc) are created for the entity or a workload has run once for the entity. Editing entity name would require recreating any existing meta / ingest /import / analytic model for that entity.