GET STARTED
DOCUMENTS
APPS
API
INTEGRATION
GALLERY
Bind the Topic to your Template

Next we'll bind our notification topic to a template via a configuration. Templates can be associated with different delivery methods (email, PDF, etc.), written in different languages (English, Spanish, etc.), and aimed at particular roles (Buyer, Seller, Origin of Goods, etc.). Here is a breakdown of the different delivery methods:

Email - send an email. The content of the email is driven from your template
Email with PDF - send an email with a PDF attachment.
PDF - this allows users to generate a PDF from the Infor Nexus user interface (NOT email). When this option is enabled, end users can select this topic from the review page on an instance of an object corresponding to the topic's target type to generate the PDF
Outbound Integration - this option can be used to send an outbound file (e.g. an EDI file). This is an advanced feature and requires configuration by an Infor Nexus employee. Please contact the developer evangelism team for more information.

Let's bind our topic to our template. Click the Add Topic button to see the screen below.

Configure the Topic
Configure the Topic

Click the Delivery Method drop down and select PDF, since we are going to be binding a PDF template with this topic. This will enable the Template dropdown, which will populate with any templates in your platform module that are PDF-compatible. Select the SampleTemplate template from the dropdown. The next two fields, Locale and Recipient Role, determine what kind of users will be able to subscribe to your notification. The locale is a reference to the language the template was written in. If you have one template written in English and one written in Spanish, you will need two templates and two notification configurations. If the user's locale preference matches the locale in the configuration, the notification will be sent using that template. If there is no match, it will try to find a match on the default locale of the user's organization. If there is no match again, it will default to English (if the only template uploaded is a locale other than English, it'll just send that). Our template was written in English, so select English from the Locale dropdown.

Next, fill out the recipient's role. Your notification may need separate templates based on the audience that will receive them. For example, a notification about a purchase order sent to a buyer might have the name of the seller on that purchase order, but it wouldn't have the buyer's name on it (because they would know their own name). It would be vice versa for the seller. In this case, you'd have two configuration and would fill out "Buyer" in the recipient role of one configuration and "Seller" in the other. If you have a generic notification that can be sent to many roles, you can add them in a comma separated list like this: "Buyer,Seller". Since our template is completely generic, type Buyer,Seller in the Recipient Role field.

For details on the Data Function field, please see Populate the Template.

Finally, set the Schema Version to 3.1 and the Target Type to Purchase Order. The Target Type should correspond to the object that will fire the notification. In this example we'll use the Purchase Order. Click the Save button at the top right of the platform module to save your work.

Once your platform module is published, your PDF should be viewable from the UI for the associated object type (Target Type) that is bound to the PDF.

NOTE: If you plan to have a Notification Topic where the Target Type is a custom object from a different platform module, then you must have an Extension Point entry on that Custom Object where Extension Point field is set to Available Actions and Query is enabled.

This Extension Point is not necessary if your Target Type is a custom object in the same platform module as your Notification Topic.
Email with PDF - More Info

The Target Type for a PDF or an Email with PDF is limited. If you select a target type that can not have a PDF generated, you will get a Validation error. All Custom Objects with the PDF feature enabled will be able to be used for PDF related topics. Native objects that can be selected for PDF related topics include:

  • ASN Type
  • Document Folder
  • First Sale Cost Worksheet
  • Goods Dispatch Detail
  • Invoice Detail
  • Order Detail
  • Order Detail / Amendment
  • Package Booking Detail
  • Packing List Detail
  • Packing Plan Detail
  • Payment Authorization Detail
  • Shipping Order
  • Transport Note Detail
  • Transport Order Shipment
  • Transport Plan Detail
Outbound Integration - More Info

The Target Type for a Outbound Integration is limited. If you select a target type that you cannot get an outbound integration for, you will get a Validation error. All Custom Objects with the Integration feature enabled will be able to be used for Outbound Integration related topics. Native objects that can be selected for Outbound Integration related topics include:

  • ASN Type
  • Document Folder
  • Goods Dispatch Detail
  • Invoice Detail
  • Order Detail
  • Order Detail / Amendment
  • Packing Plan Detail
  • Payment Authorization Detail
  • Shipping Order
  • Transport Note Detail
  • Transport Order Shipment
  • Transport Plan Detail