If you are patching DSC components through Workbench and using version numbers to track your updates, you may notice that the version of the service does not get updated. The service has actually been updated and the new functionality should be available.
This is a product issue in LiveCycle ES2 where the service version number does not get updated correctly when deploying an updated component. You can check the version numbers in Workbench after deploying the component, or you can check in AdminUI > Services > Applications and Services > Service Management:
The version numbers for the services can be updated in the component.xml file included with your DSC component JAR file. The following line is used to define the service version number:
<auto-deploy service-id=”Log” minor-version=”0″ major-version=”1″ category-id=”neo-onboarding”/>
This issue is fixed in ES3 (LiveCycle 10). There is a patch available for LiveCycle ES2 SP2 (220.127.116.11) and LiveCycle ES SP4 (18.104.22.168), so contact enterprise support if you require one of those patches.
With the fix, the service versions will be updated correctly as follows: