component plug-in

docs.appian.com/.../component-design.html

thank you stefan for you quick response.  To pull/push the data from/to the database, which approach i have to follow. Jquery or ? because we are using the appian data.

one more query can we use goJs libraries to render the UI page.?

The documentation clears says that you need to create web APIs in Appian and call these from the component. There is no direct database connection from the plugin.

any suggestion on 2 poing?

There is this:

https://docs.appian.com/suite/help/23.4/reference-js-api.html#appian.component.invokeclientapi(connectedsystem,-friendlyname,-parameters)

And then, the component plugin implements a normal behaviour, similar to other UI components. That includes saveInto logic. So you can provide data to the component and react on user interactions. For your use case this might be easier than a full API approach.

I'm mostly curious as to why you would want to do this? This is the sort of basic functionality that Appian gives you, in an easy-to-build and easy-to-maintain fashion - i.e. low-code (plug-ins are high-code by definition). What will what you are proposing give you that Appian doesn't?

i want to display the organization chart which allow me to do the modification and reflect the same in the database.

You can use this OOTB component to browse your hierarchical data:

https://docs.appian.com/suite/help/23.4/Tree_Browser_Node_Component.html

What sort of updates do you need to conduct?

i want to add/delete/modify the nodes dynamically. i think that component shows only the read only, not allow to modify.

You'll need to add the necessary configurations/code to make this work but it is do-able. 

• you can add a link on each of the nodes. This link could be an a!startProcessLink() and you can pass the node's value to the process and in that process you could retrieve the data associated with that node for editing
• to move a node you could either re-use the above process, or you can use the pathSaveInto on the hierarchy browser component as input to a separate process (say as a different link in the user interface) to effect a "move node" action