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

Hi Ben,

Thanks for the information, it very insightful.

like to check, what is the best practice or how does most smax customer, handle the smax account of user who had left their company? do they manually go in to suite admin portal to delete the record or do they make used of the OO which came with smax and automate the deletion?

Regards

Soong WengChew

Hi Ben,

Thanks for the information, it very insightful.

like to check, what is the best practice or how does most smax customer, handle the smax account of user who had left their company? do they manually go in to suite admin portal to delete the record or do they make used of the OO which came with smax and automate the deletion?

Regards

Soong WengChew

Hi Wengchew,

Most customers with a lot of "users" will invest in some form of automation, but two different schools of thought:

• HR System or IdM is prime: this means that the trigger for disabling accounts sits outside of SMAX
  • Here the automation is often triggered from another tool, or from an OO (or Connect-IT) script that is scheduled to run every X hours
  • If SSO is implemented they wouldn't be able to log in anyway, so every X=24 hours is fine
• SMAX is prime: in this case there is a Request in SMAX to disable a user
  • Here the automation triggered in SMAX is expected to update the IdM and HR systems too
  • As for the disabling of the account, we normally turn them into contacts (not delete them)
  • See: Manage Persons API - docs.microfocus.com/.../ManagePersonsAPI

You can of course handle it manually (especially if you don't have too many users):

• You can nowadays also partially manage Users in the Tenant (not just in the Suite Admin Portal)
  • https://docs.microfocus.com/doc/SMAX/2022.05/ImportUsersIntoSuite#Adding_users_manually_in_Service_Management
  • https://docs.microfocus.com/doc/SMAX/2022.05/TenantDetails (Setting: Manage users in tenant)
    

I also forgot to mention something earlier: notifications also look at the status
https://docs.microfocus.com/doc/SMAX/2022.05/APPSettings#Disable_notifications_for_person_with_selected_status

I hope this helps,

Ben

Hi Ben,

thanks for your input, it very useful.

Regards

Soong WengChew