Should a module be marked executable?

Discussions about goal-oriented and BPMN modeling.
Forum rules
Make sure every topic contains information about your LSPS version and if relevant also your server OS, client OS, database name and version, and application server name and version.
cbmeeks
 
Posts: 59
Joined: Wed Aug 07, 2013 11:28 pm

Should a module be marked executable?

Fri Oct 02, 2015 6:32 pm

I've been creating new modules and marking them as executable.
Inside the module I will have one or more processes. Each process will also be marked executable but I usually don't set their "Instantiate Automatically".

So my question is, what would be the reason to marking the global module as executable when the internal processes can be executable individually?

Thanks.

Radovan Cervenka
 
Posts: 48
Joined: Mon Feb 27, 2012 2:47 pm

Re: Should a module be marked executable?

Wed Oct 07, 2015 11:10 am

Executable modules can be instantiated - they are listed in Management Console as modules to instantiate and provide "Run As / Model" context menu in GO-BPMN Explorer. Non-executable modules cannot be directly instantiated, but can be included to executable modules. Actually, the main reason for non-executable modules is to provide "library functionality" to executable modules. For instance, modules from Standard Library are not executable.

Return to GO-BPMN

Who is online

Users browsing this forum: No registered users and 1 guest