• State Not Answered
  • Replies 5 replies
  • Subscribers 7 subscribers
  • Views 1891 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

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

paulc919
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
  • 0
    Certified Lead Developer
    I do this in jut about every project for data that does not affect process flow (meaning a model change would not be needed). It is important to allow for Lookup data to be changed, outside a release.
    Some gotchas:
    1) Never allow deletes, only deactivates otherwise you break referential integrity
    2) Make sure when processes start, they pull active only, but edits or post selection pulls the inactive incase it was selected

    I usually have an action, that gives them a TOC of all the data that they can edit (names, descriptions). Then upon selecting one, the data that can be changed. The record works too. I just do this, cause it is one screen, one place, less clicks to find and act.
Reply
  • 0
    Certified Lead Developer
    I do this in jut about every project for data that does not affect process flow (meaning a model change would not be needed). It is important to allow for Lookup data to be changed, outside a release.
    Some gotchas:
    1) Never allow deletes, only deactivates otherwise you break referential integrity
    2) Make sure when processes start, they pull active only, but edits or post selection pulls the inactive incase it was selected

    I usually have an action, that gives them a TOC of all the data that they can edit (names, descriptions). Then upon selecting one, the data that can be changed. The record works too. I just do this, cause it is one screen, one place, less clicks to find and act.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.