Installation and Configuration Guide

Back Next

Customizing Supplier 360 Workflows for Portal Users

After you customize the data model, configure the

s360-portal-workflow-config.xml

file to reflect the data model changes for workflows.

Go to the following directory:

<MDM installation directory>/app/tsr/config/

Open the following file in a text editor:

s360-portal-workflow-config.xml

If you use customized business entity fields, update the following properties based on your requirements:

Property	Description
portal.draft.path	Business entity field that stores the value of the draft indicator for a portal user.
portal.fullname.path	Business entity field that stores the full name for the portal user.
portal.portalId.path	Business entity field that stores the portal ID for portal association.
hub.admin.user	Business entity field that stores the admin user details.
portal.SupplierRegistrationView.userInd.path	Business entity field that stores values that indicate whether a user is a portal user.

If you use customized values for portal user application state, update the following properties:

Property	Description
portal.AVOSBeDraftState.Submit	Name of the user application state when a data steward submits the user details for review.
portal.direct.Submit	Name of the user application state when a business manager directly submits the user details.
portal.BECommodityApproval.Send Back	Name of the user application state when a commodity manager sends back a pending user record for additional details.
portal.BEFinancialReview.Send Back	Name of the user application state when a financial manager sends back a pending user record for additional details.
portal.BEContractReview.Send Back	Name of the user application state when a contract manager sends back a pending user record for additional details
portal.BERiskReview.Send Back	Name of the user application state when a risk manager sends back a pending user record for additional details
portal.AVOSBeFinalReview.Approve	Name of the user application state when a business manager approves a portal user.
portal.AVOSBeUpdate.Submit For Approval	Name of the user application state when a business user updates an existing portal user record and submits the changes for review.

If you have configure a customized password policy in the MDM Hub, update the same values for the following properties:

Property	Description
portal.passwordpolicy.maximumPasswordLength	Maximum length of the password.
portal.passwordpolicy.minimumPasswordLength	Minimum length of the password.
portal.passwordpolicy.minimumUniqueCharacters	Minimum number of unique characters in the password.
portal.passwordpolicy.patternValidationEnabled	Indicates whether the pattern validation is enabled for the password.
portal.passwordpolicy.passwordBeginningPattern	The character type allowed for the first character of the password when the pattern validation is enabled.
portal.passwordpolicy.passwordMiddlePattern	The character type allowed for the first and last characters of the password when the pattern validation is enabled.
portal.passwordpolicy.passwordEndPattern	The character type allowed for the last character of the password when the pattern validation is enabled.

If you use customized email templates, update the following properties:

Property	Description
portal.emailTemplate.registrationFailureC360B2BPortal	Business entity field that stores the name of the email template that is triggered when a portal user is rejected.
portal.emailTemplate.registrationSuccessC360B2BPortal	Business entity field that stores the name of the email template that is triggered when a portal user is approved.
portal.emailTemplate.internalRegistrationSuccessC360B2BPortal	Business entity field that stores the name of the email template that is triggered when a business user creates a portal user successfully.
portal.emailTemplate.updateRequestC360B2BPortal	Business entity field that stores the name of the email template that is triggered when portal user updates the user details.