Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Macros

Used for filenaming, batchingkey, “flow convoy key” and “transport convoy key”:

  • {uniqueid}  
    • Insert GUID like e.g. 66fcfec6-52f3-413a-8b7a-6a0abdef0c2e
  • {CustomDateTime$<format>} 
    • e.g. ({CustomDateTime$ddMMyyyyhhmmssffff})
  • {CustomXpath$<xpath>} 

if the first does not hit a node continue to the next:

  • { context$<ContextName>,<ContextNamespace>} 
  • FILE_{sequence$MinUnikkeSekvens,00000000}.xml” will result in ”FILE_00000001.xml”.
  • {SourceFileName} (Sets the original filename. Require the file come from FILE or FTP)
  • {SourceFileNameNoExt} (Sets the original filename (without the file extension). Require the file come from FILE or FTP)
  • {extension} (Get the default extention based on format type.)


Used for MailSubject og Mail body for stakeholder mails:

  • {Environment}
  • {DataOwner}
  • {DocumentNumber}
  • {EdiPortalLink}
  • {ApplicationServer}
  • {DocumentsId}
  • {Timestamp}
  • {Comment}
  • {ExceptionMessage}
  • {TechnicalDescription}
  • {PossibleCause}
  • {PossibleSolution}
  • {ErrorCode}
  • {ExceptionCategory}
  • {DocumentType}
  • {FaultDescription}
  • {StakeHolder}
  • {ReceiverPartnerName}
  • {SenderPartnerName}
  • {ConfigurationKey#<ConfigurationKeyName>}ConfigurationKey#<ConfigurationKeyName>#} (Without the <> like e.g. {ConfigurationKey#LINK_SLALEVEL#})
  • {ReceiverPartnerContact}
  • {SenderPartnerContact}


Mail subject and body templates are defined in

[EdiPortal].[Presentation].[tDataFieldChoices]

It is important to insert new templates with correct DataFieldsId.

This can be selected by joining

[EdiPortal].[Transport].[tTransportTypes] with [EdiPortal].[Transport].[tTransportTypeFields] 

(remember correct Dataowner)


Panel
borderStylesolid

Content on this page:

Table of Contents