Dear team,
I have submitted both the user-import and update user XML files in the database connector for comparison, along with the update user JSON. However, the update user task was triggered only after executing the provision job. It is currently pending and not completed. Could you please help resolve this issue? The job should finish running and show the changes in the target application, such as the MySQL server database.
The user import xml format is like this
<dataMapping>
<sql-query description="This is the Source DB Query" uniquecolumnsascommaseparated="emp_id">
<![CDATA[select firstname,lastname,username, emp_id,phonenumber,title,status from dbo.employee]]>
</sql-query>
<importsettings>
<zeroDayProvisioning>false</zeroDayProvisioning>
<userNotInFileAction>NOACTION</userNotInFileAction>
<generateEmail>true</generateEmail>
<userThreshold>1000</userThreshold>
<checkRules>false</checkRules>
<buildUserMap>false</buildUserMap>
<generateSystemUsername>true</generateSystemUsername>
<userOperationsAllowed>create or update</userOperationsAllowed>
<userReconcillationField>username</userReconcillationField>
</importsettings>
<mapper description="This is the mapping field for Saviynt Field name" dateformat="timestamp" incrementalcolumn="updatedate">
<mapfield saviyntproperty="username" sourceproperty="username" type="character"/>
<mapfield saviyntproperty="firstname" sourceproperty="firstname" type="character"></mapfield>
<mapfield saviyntproperty="lastname" sourceproperty="lastname" type="character"></mapfield>
<mapfield saviyntproperty="statuskey" sourceproperty="status" type="number"></mapfield>
<mapfield saviyntproperty="title" sourceproperty="title" type="">character</mapfield>
<mapfield saviyntproperty="employeeid" sourceproperty="emp_id" type="character"></mapfield>
</mapper>
</dataMapping>
Update user JSON format
{
"UpdateUserQry":[
"CALL testproc();",
"UPDATE users SET title='${user.title}', FIRSTNAME='${user.firstname}' WHERE emp_id='${user.employeeid}';"
]
}
After running the provision job its still pending only
and its not reflected in target application
Note: The after user import through user update rule based triggering the like update user
