Hi all,
We have a scenario that uses AppWorks to process manage customer requests (by internal users), with these requests coming via an integration with a web portal:
Internal Users <——> Appworks <——> Web Portal <——> End Users
The web portal is already implemented in an external non-OpenText technology and exposes it's own forms, allowing end users to register themselves and start new requests/check the status of previous requests.
In this pattern, the forms to manage/create requests have to be implemented in AppWorks (using standard Entity Modeling, that's something easy to achieve) but they also to have to be implemented in the Web Portal, with the appropriate design, business rules, etc. As an example, if we already are managing Invoices in AppWorks and the Web Portal, the moment the customer wants to start to manage Purchase Orders, the Purchase Orders forms will have to be implemented in AppWorks' Entity Modeling and also in the Web Portal (to make it available to end users).
With AppWorks being the application responsible for holding and managing the business entities, the customer is evaluating possibilitties to reduce this double-work of having forms also implemented in the Web Portal.
Given that end users are not AppWorks, nor OTDS, named-users, they don't have access to AppWorks forms, so it's not possible for them to login and use entity modeling forms.
Have you faced this pattern in the past?
Do you have any thoughts on how it would be possible to expose AppWorks entity forms to non-AppWorks users?
Thanks in advance,
Pedro
