GMSC Discussions

[mshameem]

Hi,

We upgraded a GMSC setup from v15 to v16. After installation/upgrade noticed that the custom workflow triggers (which works perfectly in v15) are not working in v16. Other workflows (that doesn't involve custom trigger) seems to be working fine in v16..

So, there seems to be something particular about custom triggers in v16.

Error report is ERROR - Controller Trigger has raised an exception in Action FireData.
Intergraph.Emea.Ioc.ObjectLoadException: Cannot load type PlotLabelTrigger.
   at Intergraph.Emea.Ioc.ObjectFactory.GetExtensibleType(String typeAlias, IEnumerable`1 assemblies)...

......

*note : 'PlotLabelTrigger' is a custom trigger type present in a dll in the bin folder.

Is there some code change to be made to make this compatible with v16. ? The settings xml as below.

workflowsettings

-------

<WorkflowRoot xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../XSD/Workflows/WorkflowSettings.xsd">
    <WorkflowNode id="10" label="Generating Dimensions..." controller="Form" form="RedlineCollection" follownode="10">
        <!-- Custom Trigger 'PlotLabelTrigger' to generate Plot Dimensions in a label feature -->
        <WorkflowTrigger name="PlotLabelListTrigger" type="PlotLabelTrigger" method="action">
            <Param name="PlotFeatureId" value="{REQUESTCONTEXT.PlotFId}" />
            <Param name="PlotId" value="{REQUESTCONTEXT.PlotId}" />
            <Param name="LabelFeatureId" value="{REQUESTCONTEXT.DimensionsFId}" />
        </WorkflowTrigger>
    </WorkflowNode>
</WorkflowRoot>

FormSettings, and error log is attached.

workflow.zip ‏3 KB

[sturcato · Accepted solution]

hi Shameem,

have you updated libraries referenced in the custom trigger project and deployed the new dll in the workflow bin folder?

Stefano

[mshameem]

Hi Stefano,

That's something to try.. Will do that. Basically a recompile on the new version and then deploy the dll.

But to me it looked like maybe this feature is being made obsolete.. ? Coz, I opened the workflow in the new gui editor. I can see the existing trigger, but I don't see a possibility to add a new custom trigger. There's other types of builtin triggers shown like SqlTrigger, MailTrigger, etc.. but I donot see a way to add a new custom trigger. So, how does that work adding a new custom trigger in v16.

Thanks,

Shameem

[mshameem]

OK. That worked by compiling with new v16 dlls.

Now, if we wanted to add this dll function as a new 'custom trigger' into a new workflow, how do we do that ? In the  workflow editor I don't see an option for adding a custom trigger. https://hexagongeospatial.fluidtopics.net/reader/GF93vUUjwjRpcBCI9g_t8Q/Z9rHwT2tY4tRmaFqGSUr2A

Thanks,

Shameem

[sturcato]

I think this is missing in workflow editor, please log a support ticket.

As a workaround you can always edit xml on the server to add your own trigger type="MyTrigger".

HTH,

Stefano

[AnilJose]

Hi Stefano,

Related to this subject, we managed to rebuild the custom dll using updated libraries and deployed new dll in workflow bin folder.

It was working fine for 16.5 version too... In both cases we were using same server (Upgraded from v15 to v16 then to 16.5).

However, we are setting up GMSC2018 new server with windows 2012 as OS . We rebuild new dll using updated 16.5 references, however

we were getting workflow error when tried to invoke custom dll trigger. Error as below:

"05.12.2018 10:07:12 ERROR - Controller Form has raised an exception in Action Index.
Intergraph.Emea.Ioc.ObjectLoadException: Cannot load type PlotCoordinatesTrigger.
at Intergraph.Emea.Ioc.ObjectFactory.GetExtensibleType(String typeAlias, IEnumerable`1 assemblies)
at Intergraph.Emea.Workflows.TriggerController.ExecuteTriggers(TriggerExecution triggerExecution, IEnumerable`1 workflowTriggerDescriptions, IWorkflowControllerContext workflowControllerContext, WorkflowData workflowData)
at Intergraph.Emea.Workflows.TriggerAttribute.ActionExecuting(ActionExecutingContext filterContext)....."

When I tried to rebuild, Target framework, I set as .NET Framework 4.5.1 in project property.

I was following the same way in the old server and here I am not able to figure out the cause of problem.

Regards,

Anil

[AnilJose]

Hi Stefano,

Regarding my doubt, it was my mistake. I copied to wrong bin folder on a hurry.

Sorry for that.

Thanks & Regards,

Anil