Hey everyone – it’s been awhile! I’ve been busy working on several projects this summer – including multiple EDMCS engagements.
One of the newest and most useful features to EDMCS is the Subscription feature, which was released in the 18.07 (July 2018) update.
Since EDMCS is such a young product, there currently is not a lot of features that support governance or approvals (however, this is *supposed* to be changing at the end of the year with approvals framework). You can read my thoughts on EDMCS’s current status with governance and how it compares to DRG workflows here.
However, EDMCS Subscriptions add a layer of governance for target systems, and allow for the sharing of master data across an organization to be collaborative and responsive.
For example, if you add a new Account to a GL Account hierarchy in EDMCS, you’d may want the FCCS hierarchy to subscribe to this update. Subscriptions allow for the GL admin to make the update, and then the system automatically passes this information along to any subscribing systems. The FCCS Admin then has the opportunity to accept (and enhance) the request for FCCS, or reject it from the FCCS hierarchy, if appropriate.
Below is an example of how to set up the Subscription feature for this scenario.
PreReqs for Subscription:
In order for Subscriptions to be set up, you need to have multiple Applications and their associated Viewpoints set up in EDMCS. We’ll continue with this example of having a “GL” app and an “FCCS” app.
General Ledger Application with Viewpoint “GL Account” for Account maintenance:
FCCS Application with Viewpoint “FCCS Account” for Account maintenance:
Setting Up Subscriptions:
To utilize Subscriptions, a Converter needs to be created between the Node Types from the Viewpoints. Navigate to the Node Type card at the top of EDMCS. Click on the “Converters” tab.
In this example, the converter will be on the FCCS_Account node type, and the source is the GL_Account Node Type.
Once the converter is set up, you can create the Subscription. Navigate to the Views card at the top of EDMCS, and select the Subscribing View, which is in this case FCCS.
Inspect the FCCS_Account Viewpoint, and navigate to the “Subscription” tab. Select “Create” and it will have a list of Nodes Types from which a converter is set up for a Subscription. Our “GL_Account” Node Type is in the dropdown.
Select the GL Account Node Type, and it will appear as a Subscription. Here, you can select a User to be assigned to the generated Request (at this time, I believe it is only specified users, not groups). This is also where you specify if the request should be “Auto-Submit” vs. “Manual Submit”. Leaving the box unchecked will make any subscription requests “Manual” and requires the specified user to intervene to accept/enhance or reject the request from their Viewpoint. Press “Save”.
Testing the Subscription
Now that I have set up my Subscription, I need to test it. I go to my “GL Account” Viewpoint in the General Ledger application and add a test node to the hierarchy:
I’ve added “Test Subscription” node under “Current Assets” in Request #1127.
I submit the Request #1127 and get a success message. I then navigate to the “Request” card.
In the Request Activity panel, I see Request #1127 that has been Completed, and then a new Request #1128, which is generated for my FCCS View, and the Request Type is “Subscription” which was generated from setting up the subscription. It’s also in “Draft” status, as it has not yet been committed to the “FCCS Account” Viewpoint, since it requires “Manual” intervention to be committed.
I also noticed, that once I submit Request #1127, I did get an email to handle Request #1128; since I was set up as the Request Assignee in the Subscription configuration:
By clicking the hyperlink in the email, it brings me into EDMCS to handle the Request #1128 and place it in my “FCCS Account” Viewpoint.
*One other thing to remember is that Viewpoints can have multiple subscriptions. This can be useful if your target application hierarchy may have multiple other applications or hierarchies it needs to update from.