The below information provides further details on steps that must be taken for CIMcloud / DM2 customers wanting to leverage the DM2 Notifications Bundle.
General information on Weblink:
Since this process is not owned by CIMCloud there may be differences in current versions. Contact DM2/PDI for current details.
In Sage the operator will initially setup a customer to receive the Weblink notifications through the standard Outbox Contacts Maintenance screen in the A/R Customer Maintenance function. (A/R Customer Maintenance Outbox Contacts button). The following screen will be displayed for any Outbox-enabled document type:
The operator will select the desired Document Type. Then set recipient type to “Weblink” and click [OK].
Weblink can be combined with email/fax recipient types for the same document.
Once a customer is setup for Weblink, Sage will consider the customer an electronic delivery customer for that document and will not print the document to a printer.
How to Use:
During the normal printing routines, Weblink notifications will be generated automatically at the time you see the “Exporting to Outbox” notification window.
- The PDF/TXT file is written to the specified network folder
- Sample file name:
- A record is written to the OBWxxx.soa table.
- If there is an active internet connection and the portal is operational, then the OBW notification record is immediately posted to the CIMcloud.
- Should the communication fail, OBW retains the record and attempts to resend the next time notifications are generated
How it Works with CIMcloud
1 – Sage owner installs the DM2 Weblinks Notifications module
After working with DM2/PDI to install Weblinks (see some general information below on Weblinks), The Sage owner will need to make sure that the documents are stored in a shared/public folder so they can be linked to from CIMCloud. The Sage owner will need to provide:
- Shared drive, accessible from MAS, to write PDF/TXT files to
- On the backend, the DM server will need to place the appropriate files in the share
- Example \\servername\shared folder
- URL to access that shared drive location from the outside world
- URL needs to be HTTPS
- Example https://remote.companyname.com/shared folder
- Directory listing should be disabled
- Place a PDF file in this location so permissions can be tested through the link
- External IP of MAS server for WSP firewall
2 – Sage owner purchases the CIMCloud Notifications Bundle
When the DM2 Notifications bundle is purchased CIMcloud will:
- Turn on the pages noted above
- Set up API authorization for DM2 notifications to be posted to CIMcloud
- Whitelist Sage owner IP addresses from servers generating the push notification
- Send Sage owner full push url from DM2/PDI to set up to push the notifications. These urls can vary based on the specific site and will contain a website and API key specific to the website.
Using this information the Sage owner will in the OB program folder, install the OBWLIB-xxx.opt file (which is similar to an INI file) received from programming (where xxx equals the company code). This contains the connection information for the client’s shared folder and the web portal.
PDFURLBASE$ : The client’s URL address to the shared drive
PDFWEBBASE$: The client’s UNC path to the shared drive
WEBLINK_URL$: The web portal’s URL address
WEBLINK_URLPATH$: The web portal’s URL subdirectory for the notifications
WEBLINK_SECURE: 0 = http, 1 = https
Sample Post to CIMCloud:
Content-Type = “application/x-www-form-urlencoded”
Charset = “utf-8”
<nm>Sample Invoice Report</nm>
<ds>DEALER #: WSP100-01</ds>
3 – Sage Owner Sets Up and Tests Notification Push
After all the above is complete Notifications should flow to the CIMcloud and display.