System Access Managent and HR process integration - Revision history

Philip Lacey: /* Setup */

2018-03-14T15:12:47Z

‎Setup

Philip Lacey: /* Usage */

2018-03-14T14:06:25Z

‎Usage

Philip Lacey: /* Usage */

2018-03-14T14:02:22Z

‎Usage

Philip Lacey: /* Security Settings */

2018-03-14T13:59:43Z

‎Security Settings

Philip Lacey: /* OnBoarding process form */

2018-03-14T13:57:40Z

‎OnBoarding process form

Philip Lacey: /* OnBoarding process form */

2018-03-13T22:32:19Z

‎OnBoarding process form

Philip Lacey: /* Rules Reference */

2018-03-13T20:55:14Z

‎Rules Reference

Philip Lacey: /* Rules Reference */

2018-03-13T20:50:17Z

‎Rules Reference

Philip Lacey at 20:49, 13 March 2018

2018-03-13T20:49:42Z

Philip Lacey: /* Leaving employment with Retired Users */

2018-03-09T13:49:57Z

‎Leaving employment with Retired Users

@@ Line 32: / Line 32: @@
 Notes
-* A field in the form is a "Basic - Staff" question type.
+* A field in the form is a "Basic - Staff All" 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.

@@ Line 79: / Line 79: @@
 = Usage =
@@ Line 89: / Line 91: @@
 # The user modifies the account settings as normal and ensures the status is set to "Live"
 # The system will perform the settings above and link the new account to the record by updating the staff field and transferring any mapped data as necessary.
 === Support catches ===
@@ Line 94: / Line 98: @@
 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.
@@ Line 119: / Line 126: @@
-The next part of the process is to configure the system to react when a user is set "Retired". ''Main Menu > System Access Management > System Management > System Settings > HR Retire user''
+The setup is the same for Live as Retired but the section in System Settings is different.
-[[File:SAMHR_retireuser_000.png|800px]]
+Configure the system to react when a user is set "Retired". ''Main Menu > System Access Management > System Management > System Settings > HR Retire user''
@@ Line 129: / Line 136: @@
 Save the settings and then go back into the settings and some more fields will be visible.
-[[File:SAMHR_retireuser_001.png|800px]]
+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.
-* From the drop down list choose the Staff question that was added above.
+=== Support catches ===
-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.
+The engine also works with the Group Retire function.
-=== Retire - Data Protection Rules ===
+= Retire - Data Protection Rules =
@@ Line 166: / Line 175: @@
 === Usage ===
 = Rules Reference =

@@ Line 78: / Line 78: @@
 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.
-=== Usage ===
+= Usage =
-# A ticket or work item comes into the Form to create / make live a new person.
+In the form a new user needs to be added to the system
 === Support catches ===

@@ Line 73: / Line 73: @@
 * From the drop down list choose the Staff question that was added above.
-* Choose the outcome "Account Live" as created above.
+* Choose the outcome "System 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 these are described below in the rules section.
 === Usage ===

@@ Line 29: / Line 29: @@
 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
-A field in the form is a "Basic - Staff" question type.
+Notes
-* An outcome is set along the lines of "New Account".
+The "Pass details to SAM" outcomes need URLs added to the 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.
-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
- ../security/userUser_Lookup-details.asp?strData_URL=userUser_Copy-confirm.asp&intCDA_Id=--intCDA_X_Id--&strFirstname=X&strSurname=X
+A sample Copy User url would be
-Please note for the replacement to work the X in the intCDA_X_Id is the Id of the form the outcome is being used in.
+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 ===

← Older revision		Revision as of 22:32, 13 March 2018
Line 44:		Line 44:


		+	Please note for the replacement to work the X in the intCDA_X_Id is the Id of the form the outcome is being used in.

	=== Security Settings ===		=== Security Settings ===

@@ Line 167: / Line 167: @@
 * 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]]

@@ Line 163: / Line 163: @@
 = Rules Reference =
-The format of this is XXXX=--YYYY--[[##]]
+The format of this is XXXX=--YYYY-- [ [ # # ] ]
 * Where XXXX is the strCDA_X_field_y_Z of the form.

@@ Line 68: / Line 68: @@
-There are other extra settings which allow multiple fields of information to be copied into the form. The format of this is XXXX=YYYY
+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.
@@ Line 136: / Line 132: @@
-There are other extra settings which allow multiple fields of information to be copied into the form. The format of this is XXXX=YYYY
+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.
@@ Line 168: / Line 160: @@
 === Usage ===

@@ Line 95: / Line 95: @@
 == Leaving employment with Retired Users ==
@@ Line 100: / Line 103: @@
-=== Security Settings ===
+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.
 === Security Settings ===
@@ Line 130: / Line 141: @@
 * YYYY is the HR field or Client field as available from the reference tables.
 * Date time replacements are also supported.
 === Retire - Data Protection Rules ===
@@ Line 150: / Line 163: @@
 As many rules as required can be applied across bxp.
 === Usage ===