Hi all, we are in middle of planning for complete moving data from apps to

natasav over 9 years ago

Hi all,
we are in middle of planning for complete moving data from apps to tempo interface.
We had a several discussions of what is appian best practise for doing that.
Now wee have several question about records. On the system customer wants to keep all data permanently , so we suggest to do some king of archiving or saving necessary data in SQL database and displaying those data by using tempo report and tempo records in same manner as portal reports and process instance dashboard.
So my question is it possible to set security on record data per instance or entry level in same manner as process instance security? And if it's possible how can we do it?
And on the other hand how can we display a html data by using sail?
BR,Natasa

Discussion posts and replies are publicly visible

Parents

0 Chris over 9 years ago

@sikhivahans - Our requirements are typically that multiple users should be able to see a record item, say, process initiator, approver 1, approver 2, approver 3 - where 3 approvers are dynamic based on initiator's user profile, department, etc. While we can apply the filter value for loggedinuser() in entity-backed and show records for the initiator, we are unable to filter based on other fields simultaneously due to the restrictions of not having access to rf! data within the value setting on the filter - or the ability to 'OR' the default filters ('AND' is forced). Generally speaking, any user should be able to access the record and see only items for which they have either initiated or approved. After multiple conversations on forum and with Appian, there was no clean OOTB solution to this aside from process-backed records, so we went with service-backed due to flexibility there. Process-backed records are not feasible for us due to the size of our environment.

We had a lengthy discussion on forum regarding this topic at the time as well (https://forum.appian.com/suite/tempo/entry/e-155229).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 9 years ago

@sikhivahans - Our requirements are typically that multiple users should be able to see a record item, say, process initiator, approver 1, approver 2, approver 3 - where 3 approvers are dynamic based on initiator's user profile, department, etc. While we can apply the filter value for loggedinuser() in entity-backed and show records for the initiator, we are unable to filter based on other fields simultaneously due to the restrictions of not having access to rf! data within the value setting on the filter - or the ability to 'OR' the default filters ('AND' is forced). Generally speaking, any user should be able to access the record and see only items for which they have either initiated or approved. After multiple conversations on forum and with Appian, there was no clean OOTB solution to this aside from process-backed records, so we went with service-backed due to flexibility there. Process-backed records are not feasible for us due to the size of our environment.

We had a lengthy discussion on forum regarding this topic at the time as well (https://forum.appian.com/suite/tempo/entry/e-155229).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data