Anonymous, bureaucrat, administrator
7,528
edits
Changes
m
* An outcome is set along the lines of The "New AccountPass details to SAM"outcomes need URLs added to the process. The fastest setup is to copy a user as this also copies permissions.* A second outcome It is "Account Live"possible to pass information through the parameters to speed up the creation process.
The "New Account" outcome needs a URL added to it's process. The fastest setup is to copy a user as this also copies permissions. It is possible to pass information through the parameters to speed up the creation process.A sample Add User url would be
A sample url would be
A sample Copy User url would be ../security/userUser_Lookup-details.asp?strData_URL=userUser_Copy-confirm.asp&intCDA_IdstrFirstname=--strCDA_1443_field_1_2--&strSurname=--strCDA_1443_field_3_2--&strMobile=--intCDA_X_IdstrCDA_1443_field_0_6--&strFirstnamestrEmail=X--strCDA_1443_field_0_7--&strSurnameintCDA_Id=X--intCDA_1443_Id--
* Where XXXX is the strCDA_X_field_y_Z of the form.* YYYY is the HR field or Client field as available from the reference tables.* Date time replacements are also supported.= Usage =
=== Usage ===In the form a new user needs to be added to the system
→Setup
The first stage is to define an on-boarding process. This is essentially a checklist of things to do when the person becomes an employee. This can be built using a form in Form Management
[[File:hrandsam_001.png|800px]]
Notes* A field in the form is a "Basic - StaffAll" question type. (Make sure it's All or the retired users will not work properly.)* There are four outcomes to signify the different events that can happen** "System Managed - User Added" will be used when the system has a user add.** "System Managed - User Retired" will be used when the system has a user retire event.** "Pass details to SAM - Add User" in this example will be used for an add user process** "Pass details to SAM - Copy User" in this example will be used for a copy user process.
../security/userUser_Add_Security-details.asp?strFirstname=--strCDA_1443_field_1_2--&strSurname=--strCDA_1443_field_3_2--&strMobile=--strCDA_1443_field_0_6--&strEmail=--strCDA_1443_field_0_7--&intCDA_Id=--intCDA_1443_Id--
Please note for the replacement to work the 1443 in the intCDA_1443_Id is the Id of the form the outcome is being used in. This also applies to the fields being used.
=== Security Settings ===
* From the drop down list choose the Staff question that was added above.
* Choose the outcome "Account LiveSystem Management - User Added" as created above.
There are other extra settings which allow multiple fields of information to be copied into the form. The format of this is XXXX=YYYYthese are described below in the rules section.
== Generic description ==
# A ticket or work item comes into / is data entered into the Form to create / make live a new person.# The outcome "New AccountPass details to SAM - Copy User" is chosen.# The Administrator person using bxp chooses the account to copy(as per the normal copy user process)# The user adds modifies the account settings as normal and sets ensures the user status is set to "Live"# The system will perform the sittings settings above and link the new account to the record by updating the staff field and transferring any mapped data as necessary.
If the CDA Id isn't passed to the form the system will still work. The system will create a new record in the nominated form and add the staff Id to that record. The system performs a look up to match the CDA record will create a record where not match is found. If the CDA is passed the system will update the CDA record specified.
Although an outcome is selected not all the functionality of the outcome is executed by the SAM module. The naming and linking to the outcome is just to allow outcomes in the form be used as follow up.
== Leaving employment with Retired Users ==
If a staff member was on boarded there is probably going to be an exit process to be followed as well. bxp can facilitate automation of a lot of the process.
=== Exit process form ===
Step 1 is to build a form that has the exit process built into it. This form can take a multitude of security steps, of HR steps and of business steps as well.
As with the recruitment. There needs to be a staff field in the form. An outcome to process the staff members leaving is also useful.
The leaving process may begin with a notification of intent to leave, which would result in the account not being "Retired" immediately. Alternately the process begins with deactivating the user's bxp account which is immediate removal.
The setup is the same for Live as Retired but the section in System Settings is different. Configure the system to react when a user is set "Retired". ''Main Menu > System Access Management > System Management > System Settings > HR Retire user'' Enter the Form Id for the Form created above. Save the settings and then go back into the settings and some more fields will be visible. * From the drop down list choose the Staff question that was added above.* Choose the outcome "System Managed - User Retired" as created above. There are other extra settings which allow multiple fields of information to be copied into the form. The format of these are described below in the rules section. ===Support catches === The engine also works with the Group Retire function. = Retire - Data Protection Rules === [[File:retire_dataprotectionrules_001.png|800px]] It is also possible to create a range of rules to be executed to update other forms and associated data throughout bxp. These rules are independent of the HR Retire User rules which only occur on one form. The rules placed here are more wide ranging and all for greater system flexibility in data protection, HR management and also work management. * Type : AllForms, Form, Metadata, Reminders* Engine : Delete, DeleteCDA, DeleteCCL, Update, Run* Form Id | Program Id* New User Id The rules will take the format of Type-Engine-FormId-NewUserId; As many rules as required can be applied across bxp.
=== Usage ===
= Rules Reference =
The format of this is XXXX=--YYYY-- [ [ # # ] ]
* Where XXXX is the strCDA_X_field_y_Z of the form.
* YYYY is :
** A Client field [[Client_table_fields]]
** A -- standard field replacements (including date time replacements) [[Standard_field_replacements]]
** A value (simply don't wrap the field in -- characters)