Other Functions

Dictionary key for the rule's message location.

Where the message will be displayed. Options are attribute (default) and top.

Dictionary key for the rule's message.

The message to be displayed for the violated constraint.

Dictionary key for the rule's operator.

Operator used to evaluate constraint, as in Simple Constraints.

Dictionary key for the rule's values.

Tilde-delimited values used to evaluate constraint, as in Simple Constraints.

Generic key used to determine the current configuration context.

The variable name of the commerce process or external application identifier.

The BM_PARTNER_SECURITY_TOKEN parameter represents the WSSE security Username Token for SOAP, used for sending stateless SOAP with UrlDataByPost.

Example:

 ...<soapenv:Header><ClientName xmlns="urn:crmondemand/ws">Bigmachines</ClientName>"+BM_PARTNER_SECURITY_TOKEN+"</soapenv:Header>...

Inserts the block

<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity- secext-1.0.xsd"><wsse:UsernameToken><wsse:Username>User'sPartnerLogin</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">User'sPartnerPassword</wsse:Password></wsse:UsernameToken> </wsse:Security>

Generic key used to determine prior configuration context.

Projected state of the asset calculated for a requested date.

Reason exists in the user-side tree and it is approved by all approvers, therefore the reason is completely approved.

Reason exists in admin reason tree but the condition for the reason is not met, therefore no record for it exists in the user-side tree.

No reason exists in admin reason tree with given variable name.

Reason exists in the user-side reason tree and there are pending approvals.

Reason exits in user-side tree, but has been rejected by at least one approver.

Approved Status. This is used in Remote Approvals in the tilde separated approval history to be returned in the BML in Approve/Reject action

Example:

returnString=returnString+ApproverName+"~"+ApproverCompany+"~"+ApproverDate+"~"+BM_REMOTE_APPROVAL_STATUS_APPROVED+ "~" + ApproverComment +"~||";

Custom Status. This is used in Remote Approvals in the tilde separated approval history to be returned in the BML in Approve/Reject action. This can be used for anything other than Approved/Rejected

Example:

returnString=returnString+ApproverName+"~"+ApproverCompany+"~"+ApproverDate+"~"+BM_REMOTE_APPROVAL_STATUS_CUSTOM+ "~" + ApproverComment +"~||";

Rejected Status. This is used in Remote Approvals in the tilde separated approval history to be returned in the BML in Approve/Reject action

Example:

returnString=returnString+ApproverName+"~"+ApproverCompany+"~"+ApproverDate+"~"+BM_REMOTE_APPROVAL_STATUS_REJECTED+ "~" + ApproverComment +"~||";

Sales BOM used for launching configurator.

Constant for 'Leave Value Unchanged' for Date.

Return Type:  Date

Example:

Consider a date array dateArr = Date [] {getdate, getdate}.

If you want to keep the value of dateArr[0] unchanged, specify the following:

dateArr = Date [] {$BM_UNCHANGED_DATE$, getdate};

Constant for 'Leave Value Unchanged' for Number. This is used to specify an array value that should remain unchanged.

Return Type:  Numeric

Example of:

Consider an int array intArr = Integer [] {1,2,3}.

If you want to assign new values to intArr[1] and intArr[2] but keep intArr[0] = 1, specify the following:

intArr = Integer [] {$BM_UNCHANGED_NUM$, 21,23};

Constant for 'Leave Value Unchanged' for String.

Return Type:  String

Example:

Consider a string array strArr = String [] {"a","b"}.

If you want to keep the value of strArr[0] unchanged, specify the following:

strArr = String [] {$BM_UNCHANGED_STR$, "abc"};