- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2024 01:11 PM
For certain catalog items it is necessary to gain approval from a user who is associated with the submitters organization. The users who are designated as these senior level approvers for an organization are not necessarily a member of that organization. On some catalog items we need to present the submitter with a list of possible senior level approvers based on their organization.
Looking for some advice on how we might be able to store this information using OOTB features.
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2024 02:03 PM - edited ‎09-26-2024 02:04 PM
I would say you should create a decision table (OOB) With inputs organization + output senior level details
Otherwise create a customer table if you are not aware of decision tables
Based on submitter Org ,we can show available senior level approvers in list collector variable/ref varibale
For other items ,if seniors are not part of submitter org just use condition selected seniors org is equal to submitter org or not based on that show the data in variable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2024 02:03 PM - edited ‎09-26-2024 02:04 PM
I would say you should create a decision table (OOB) With inputs organization + output senior level details
Otherwise create a customer table if you are not aware of decision tables
Based on submitter Org ,we can show available senior level approvers in list collector variable/ref varibale
For other items ,if seniors are not part of submitter org just use condition selected seniors org is equal to submitter org or not based on that show the data in variable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2024 11:06 AM
Trying to avoid custom tables. Although maybe extending an existing table would work
The Decision Table appears to do exactly what we need. Easy to maintain the data and incorporate into a Flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2024 11:28 AM
Yes go for decision table itself
Mark it accepted as solution if it is helpful