Feature - iAccess handler check utility#90
Feature - iAccess handler check utility#90SapphicFire merged 6 commits intoServiceNowDevProgram:mainfrom
Conversation
…nd attach to task record based on input parameters.
…r existing task record.
…finition_163e8dfe8358325025abc070ceaad38f.xml
…d a user to determine what roles a user would need in order to be able to edit fields on the group record.
|
🚫 Unexpected files changed in PR Thank you for your contribution. However, it seems that the file changes in this Pull Request are incorrect or invalid. Allowed patterns: Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one. If you feel that this PR should be accepted in its current state, please reach out to Astrid Sapphire (SapphicFire) on GitHub, or in the SNDevs Slack Hacktoberfest channel. |
|
@SapphicFire It looks like automation isn't correct to validate PR file changes. I see that this PR has only required file changes. Can you please look into it? |
|
It looks like automation isn't correct to validate PR file changes. I see that this PR has only required file changes |
|
I am going to re-run the action in debug, please disregard the following closure as I will reopen |
|
🚫 Unexpected files changed in PR Thank you for your contribution. However, it seems that the file changes in this Pull Request are incorrect or invalid. Allowed patterns: Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one. If you feel that this PR should be accepted in its current state, please reach out to Astrid Sapphire (SapphicFire) on GitHub, or in the SNDevs Slack Hacktoberfest channel. |
|
As with bkb's fork, there wasn't a merge base found. Will update the automation |
Created a flow designer action which to determine what roles a user would need in order to be able to edit fields on the group record.
This will be useful to troubleshoot access issues for scoped app to find out which user can edit group records based on role hierarchy.
This flow designer action has below input parameters: