Support for abstract task to be treated as non executable nodes in RHPAM modeling

This is a customer reported issue: 

As we understand RHPAM currently doesn’t support inclusion of an abstract task in the BPMN model. We need to specify the task type in order to compile and build the model. Since the customer has other BPMN 2.0 modeling tools they are looking for interoperability, and a way by which the abstract task can be treated as a non executable node as the design progresses in to a fully functional model.

Customer Feedback: Some tasks could be collapsed to one because of the implementation of the automation framework, but there is value in maintaining separate tasks so that the business/sme has a common understanding on what the automation is doing to maintain readability.  These are still standard bpmn workflows and should import without an issue but in RHPAM errors in validation occur.