Role extensions
Revision as of 09:09, 3 December 2019 by Administrator (talk | contribs) (Created page with "Role extensions are extensions points for a role. == Parameters == == Documentation == == Inheritance == == Helper functions/classes == == Discovery of role extensions ==...")
Role extensions are extensions points for a role.
Contents
Parameters
Documentation
Inheritance
Helper functions/classes
Discovery of role extensions
Role extensions are discovered in the following order:
- Workflow scripts that are children of roles in parent folders with same name. I.E. if the current role is named R1, and is located in the Path \Products\Dashboard1\Company A\Dept B, then it will look for role extensions in
- \Products\Dashboard1\Company A\Dept B\R1
- \Products\Dashboard1\Company A\R1
- \Products\Dashboard1\R1
- \Products\R1
- \R1
- Generic scripts may be defined in folders named "Role exts" in any of the parents. I.E. followng the example from above the following folders are examined:
- \Products\Dashboard1\Company A\Dept B\Role exts
- \Products\Dashboard1\Company A\Role exts
- \Products\Dashboard1\Role exts
- \Products\Role exts
- \Role exts
- If the current user does not have read access to the role extension itself, then the extension is ignored.
- If multiple role extensions are found with the same name, then only the first one found is "discovered". But it is possible inside a role extension to call the "parent" version of the role extension.
