When suppliers are invited to your partner portal, a default email message is configured
for them. The email message automatically uses the organization name, primary color, and portal URL
that are defined in your TenantParameters. However, you can configure the email
message to override the default message.
About this task
A user who has both the admin and builder role in the IBM®
Envizi™ Supply Chain
Intelligence
application can use the following procedure to configure the partner portal invitation email
message.
You can include the following variables, which are enclosed in double braces as shown, in the
message body. The variables are evaluated when the message is sent.
- {{payload.tenantParameters.brandInfo.organizationDisplayName}}
- {{payload.supplier.primaryContact.firstName}}
- {{payload.tenantParameters.brandInfo.primaryColor}}
- {{payload.tenantParameters.brandInfo.url}}
You can pass in more variables from the notification rule but it is an advanced operation that
is beyond the scope of the following procedure.
Procedure
- Configure the email message:
- In the Envizi Supply Chain Intelligence application, click Message
builder.
- Click Portal invite for scope 3.1 and then click
Copy.
- Enter a name and a logical name.
The logical name is for organizational
purposes and is not shared in outgoing emails.
- Click .
- Edit Message subject and Message body as
required and then save.
To edit the message body, use either the HTML
edit tab or the HTML source tab.
- Override the default email message:
- Click Card builder.
- Click the Filter icon and under Other card types, select
Button and then click Apply filters
- Select the Preview Email Button card, select Create
an override from the overflow menu, and then click
Continue.
- To edit the source, click </>.
- Scroll down and find the text
resources[1].request.body
, then replace
the text portalInviteForScope31
with the logical name of the message that you
created previously and click Done.
{
"name": "resources[1].request.body",
"values": [
"{ \"emailMessageTemplateLogicalName\": \"portalInviteForScope31\", \"notificationType\": \"email\", \"contacts\": [{\"firstName\": \"{{$root.viewData?.IBMMeta?.userFirstName}}\", \"lastName\": \"{{$root.viewData?.IBMMeta?.userLastName}}\", \"emailAddress\": \"{{$root.viewData?.IBMMeta?.userEmail}}\"}], \"primaryBusinessObject\": [\"Organization\"], \"type\": \"notification\", \"tenantId\": \"{{tenantId}}\", \"name\": \"{{$root.viewData?.IBMMeta?.userFirstName}}\", \"additionalInfo\": [{\"name\":\"supplier.primaryContact.firstName\", \"value\":\"{{$root.viewData?.IBMMeta?.userFirstName}}\"}, {\"name\":\"supplier.primaryContact.lastName\", \"value\":\"{{$root.viewData?.IBMMeta?.userLastName}}\"}, {\"name\":\"tenantParameters.brandInfo.url\", \"value\":\"{{$requests[0].output.brandUrl}}\"}, {\"name\":\"tenantParameters.brandInfo.primaryColor\", \"value\":\"{{$requests[0].output.primaryColor}}\"}, {\"name\":\"tenantParameters.brandInfo.organizationDisplayName\", \"value\":\"{{$requests[0].output.orgDisplayName}}\"}, {\"name\":\"objectId\", \"value\":\"{{$requests[0].output.objectId}}\"}], \"specialRenderingMode\": \"DEFAULT\" }"
],
"metaInformation": "resourceOption"
},
- To test the new email message, click Preview email and check your
email inbox to ensure that the email renders as you expect.
- In a separate tab, modify the message in the message builder as
necessary.
- Click Save to save the override.
You can delete the override at any time to return to the default
state.
- Create and activate a rule for the new email message.
- Click Rule builder.
- Select the Send invite for scope 3.1 rule and click
Copy.
- Remove the text - copy from the name field.
Important:
Ensure there is a space after 3.1 in the rule name. If an error related to the unique name of the
rule is detected, add a space after the rule name.
- Update the logical name to a unique name.
- Click Configure and scroll to Actions, then click the Email
Edit icon.
- On the Add action page, under Message, select the message that
you created previously, click Done and then
Save.
- Activate the Send invite for scope 3.1 rule that you created
and deactivate the original rule.