This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Departments where you need more than PersonHead and PersonHeadSecond

Hi,

Hypothetical question...

Suppose a company has different middle or lower management tiers in a department, so it does not just have a manager and deputy, it can have several managers in different capacities.

If a customer needed attestation and approval logic in addition to just having a schema extension allowing more FKs to a Person object than just UID_PersonHead and UID_PersonHeadSecond, what would be the best way to extend the solution?

A very simple example:

Suppose a customer wanted some way for department managers to set a named commissary and a deputy at the department level. These people might act as approvers for certain types of asset-related requests, and be responsible for some attestation and audit.

Not all departments would need their own commissary/deputy, if a commisary in a parent or grandparent department can handle it.

Option 1: we could represent this through an attribute on the Person object, and the approval logic would need to find one of the two people tagged with a given property who's adjacent or above the requestor in the org structure, to work out who the approvers are. Attestation campaigns might be quite fiddly to configure though.

Option 2: we could extend the Department table with UID_Commissary and UID_CommisarySecond fields (equivalent to UID_PersonHead and UID_PersonHeadSecond), create a HelperCommisaryOrg table that performs a similar function to HelperHeadOrg, and so on.

Any others?