Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
3 replies
Subscribers
6 subscribers
Views
2082 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi all, We have requirement where we want to use Appian workflow capa
rahulk828
over 11 years ago
Hi all,
We have requirement where we want to use Appian workflow capability using third party UI framework that will integration with Appian for the workflow purpose. So we have requirements like:
1. Need to get logged's in user worklist.
2. Extract data from tempo feeds, records and reports
3. Actions data to start the process model and other details.
Apart from this I have search the Appian 7.3 documentation for the available APIs and found package named "com.appiancorp.suiteapi.process" with few class having operations or function related to process. I wan to understand whether it is recommended to use this package or other such package for the integration purpose of appian with external UI framework.
Please reply....
OriginalPostID-99067
OriginalPostID-99067
Discussion posts and replies are publicly visible
Parents
0
venkats533
over 11 years ago
a process is a mix of scripted tasks and user input tasks. what you are trying to do is to remove ALL user input tasks from the process flow and make several services out of one process flow. you wish to use these services in an external UI. by following this design, you are essentially orchestrating the workflow out side of Appian. I don't think that is best practice and you will lose all mobile ability of Appian. With new 7.4 version, Appian user input form supports a lot of advanced features. I don't know the reason to use external UI and do all that hard work of design, code and test when a simple drag and drop or SAIL expressions can be used ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
venkats533
over 11 years ago
a process is a mix of scripted tasks and user input tasks. what you are trying to do is to remove ALL user input tasks from the process flow and make several services out of one process flow. you wish to use these services in an external UI. by following this design, you are essentially orchestrating the workflow out side of Appian. I don't think that is best practice and you will lose all mobile ability of Appian. With new 7.4 version, Appian user input form supports a lot of advanced features. I don't know the reason to use external UI and do all that hard work of design, code and test when a simple drag and drop or SAIL expressions can be used ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data