User person status Retired, Terminated, Inactive, handling of terminated user.

Hi All,

Seeking advise on SMAX OOB practice use of the person status.

the value in people -> person status, does having different status trigger any task or feature in SMAX or are these just pure status value input?

example:

when set a person status to either retired or terminated or inactive does it prevent the user from logging in?

when set a person status to either retired or terminated or inactive, will smax auto delete the user account in BO (suite adamin) portal and change the record to contact?

OOTB how does smax handle user account which no longer required access?

In smax is there a way to automate to remove the user account in BO when the user status is set to inactive or terminated?

(can this be done with the OO that came with smax in premium lincesne.)

Regards

Soong WengChew

Tags:

Parents
  • Hi Soong WengChew,

    I won't be able to give you every usage here, but the status is often used to limit the number of people shown in a (Many2Many or Entity Link) dropdown.

    In Requested By for instance you will find that the system automatically filters out certain status values (you can see which ones by doing F12 and checking the REST-API):

    • Person?filter=(((IsSystemIntegration+!=+'true'+and+IsSystem+!=+'true'+or+IsSystemIntegration+=+null)+and+((EmployeeStatus+!=+'Retired'+and+EmployeeStatus+!=+'Terminated')+or+EmployeeStatus+=+null)).. 

    The above filter is predefined by SMAX.
    However, the system doesn't automatically change the User into a Contact based on this (see 'Person type' field).

    You can add more Rendering rules in case you want to add behaviour for other status values, especially if you add more values to the "Employee status enum" list. 

    Regards,

    Ben

    Ben Rabau

Reply
  • Hi Soong WengChew,

    I won't be able to give you every usage here, but the status is often used to limit the number of people shown in a (Many2Many or Entity Link) dropdown.

    In Requested By for instance you will find that the system automatically filters out certain status values (you can see which ones by doing F12 and checking the REST-API):

    • Person?filter=(((IsSystemIntegration+!=+'true'+and+IsSystem+!=+'true'+or+IsSystemIntegration+=+null)+and+((EmployeeStatus+!=+'Retired'+and+EmployeeStatus+!=+'Terminated')+or+EmployeeStatus+=+null)).. 

    The above filter is predefined by SMAX.
    However, the system doesn't automatically change the User into a Contact based on this (see 'Person type' field).

    You can add more Rendering rules in case you want to add behaviour for other status values, especially if you add more values to the "Employee status enum" list. 

    Regards,

    Ben

    Ben Rabau

Children