I'm currently developing a reference maintenance function and wondered if an

I'm currently developing a reference maintenance function and wondered if anyone had already done something similar ? The rationale is that we can give maintenance function to trusted Business reps so they can maintain the reference data used in Appian processes or exposed to other systems, things like Pension Annual Allowances (changed by UK Government), Document Hyperlinks (changed as and when the URL is amended).

I'm currently using a combination of Records and related actions to Add or Edit entries (as per the attachment) and wondered if this approach is a good idea or if there are some existing patterns I could plug into ?

Thanks

Paul

Reference Data Maintenance.docx

OriginalPostID-198324

OriginalPostID-198324

  Discussion posts and replies are publicly visible

Parents
  • We do this as well, wherever possible. Similar to the considerations above, I will often record 2 data bits for any field selection where options are editable by our functional owners - one for the chosen ID of the entry/option, and one for the value at selection time. This allows you to display the option as shown at task completion time, as well as retaining the ID for situations where you may want to display currently updated data, vs what it was during selection - depending on process considerations. Different types of data will require different theory there.
Reply
  • We do this as well, wherever possible. Similar to the considerations above, I will often record 2 data bits for any field selection where options are editable by our functional owners - one for the chosen ID of the entry/option, and one for the value at selection time. This allows you to display the option as shown at task completion time, as well as retaining the ID for situations where you may want to display currently updated data, vs what it was during selection - depending on process considerations. Different types of data will require different theory there.
Children
No Data