Stephan Fischli
Forum Replies Created
-
AuthorPosts
-
Rute,
Do you have a valid license installed?
If there is no valid license installed (commercial or even evaluation license key) you will be able to start PM21 10 or 20 times. When this counter has exceeded, you should see a text “unlicensed” on every shape.
If your license is correct, do you have this effect for every new diagram created (means if you start PM21 from windows Start menu)? Or is this behavior coupled on a specific diagram? If yes, could you please attach an example?
Please ensure, that your installation was successfully.
Tnx.
Stephan.Post Edited (01-09-06 00:50)
I did post a feature request for wizzarding Process Documentations.
In Version 2.1 you can store your BPD as html (save as… choose html) and you will get a nice HTML representation of your BPD (best looking with IE 6 and activeX enabled).
Simon,
BPMN defines the attribut ConditionExpression that can be set to “None”, “Expression” or “Default”. If Expression is set, there must be set an ConditionExpression (Type String).
In PM2.0 you have to set all outgoing sequence flows for a gateway to “ExpressionType” = “Expression” or “Default” via AttributExplorer on each SequenceFlow. If ExpressionType is set to Expression, you have further to define a ConditionExpression (something like True, False or an XPath expression – whatever you like).This behavior is quiet strenuous for the User.
So we added following convenience functions to Version 2.1:
1. Outgoing Sequence Flows will be set by Default to ConditionType = Expression and will have an Default ConditionExpression = “True”. This allows to model straight forward without any breaks configuring the gateways.
2. You will be able to get a ConditionEditor if using Context Menu “Conditions…” on the Gateway itself (this is what users expect). Now you can define the conditions for each outgoing sequence flow in one specific dialog.Hope this helps
Regards,
StephanKiran,
Actually the only way to do that could be your own macros or your own master shape in Visio (preconfigure a Task with your wsdl operations).For the next version of Process Modeler you will have the backward synchronization feature which allows you to read instrumented .bpel files back into Process Modeler. A solution could be made via xml file automation (xslt conversion).
Regards,
StephanKirnar,
Points one to five will match pretty good.You can import the wsdl files from the filesystem or an URL (webserver or repository) into Process Modelers Object Model.
Your question was:
“As we have already assigned a wsdl location and the operation name to each task (as attributes), use that information while exporting to BPEL instead of taking user’s input again.”Process Modeler will fill up the necessary BPMN attributes as good as possible (taken from the wsdl file, the target namespace definition etc.).
Then, if exported, Process Modeler will create a runnable .bpel file. Several information can also be defined afterwards (ex. in ORCALE BPEL Designer).The future version of Process Modeler will allow to import such modified .bpel files back to the BPMN model. So you will get a proper roundtrip communication between the analytical and technical process model.
Probably I did not yet understand very well the question you had?
Stephan.
Bill,
1.) The Attribute Explorer has two modes: USER MODE and EXPERT MODE. You can switch with the button in the right upper corner (small head).
Attribute Condition Type is per default visible in Expert Mode only.2.) Condition Type and Condition Expression must be defined in the outgoing sequence flows. Did you try this?
If your Gateway is of type XOR/OR you have to set the Condition (Condition Type = Expression and Condition Expression must be set, ex. true or false).BTW: We did identify this situation as a problem also for users and we will fix this in one of the next service releases with a better default behavior of Gateway/SequenceFlow situations.
Stephan
Is it possible to poste your visio file?
Thanks
StephanWhat do you mean with “logically associate the event with the task”?
I guess you mean that the intermediate event shape is not connected with the underlaying task shape. We do not group or connect overlayed shapes automatically but we detect this pattern by valdidating the diagram or while editing attributes in the attribute explorer.Try this:
– get a task shape
– place an intermediate event on its border
– set the Trigger attribute to “compensation”
– get another task and connect it with the intermediate event (via an association shape).
– set the associations Direction to this new compensation taskNow you will see, that the compensation task will automatically change his symbol to “compensation” (left arrows on the bottom).
To edit such overlayed shapes you just have to select both and move them together.
Stephan
Janko,
It’s true. There is not too much literature today in the book stores. But on the net, you can find several interesting and useful information. Try also http://www.bpmi.org or http://www.bpmn.org.
I’am sure that this will be fixed in the next several month because BPMN is heavily growing. For best practice exams or show cases, you would probably have to publish these models. Exactly this is the problem: process models are typically not for public eyes.Best regards
StephanYes. Process Modeler 2.0 supports 100% of the BPMN specification (includes all attributes).
An example for this would be an intermediate timer event on the “border” of an activity.Reagards
StephanThis dialog will always appear if there is no PM1.1 installation found on the PC. Click OK and then it should appear a dialog which asks you for conversion from an older verison to PM 2.0. Does this happen?
If yes, say yes and PM2.0 will redraw your diagram. Then you have to give a new filename and save the diagram as a new version 2.0 diagram (the original diagram will not be overwritten).
Reopen this diagram and you can work with it as usual.If no, there is something wrong with your PM2.0 installation. Version 1.1 must not be installed to convert diagrams.
So uninstall PM2.0 and reinstall it clean (you must have adninistrator rights on the PC).Hope this will help.
StephanWe need a bit more information about your environment. Could you please tell us the OS and Visio versions of your installation and the EXACT steps which you did (if you still know this)?
There is one known ‘path’ to such a behavior. If you have an older Preview and you did not uninstall this before you reinstall, the installer could produce such a behavior.
The bad news is, that this has something to to with the Microsoft Installer/Uninstaller and we did not yet understand what exactly hapens in this situation.
What you can try (but be carefully): remove all keys with the pattern “Process Modeler” or “ITpearls” from your registry (regedit) and then delete the Process Modeler Installation Directory manually
Please note: THIS IS NOT THE PREFERRED AND CORRECT WAY TO UNINSTALL PROCESS MODELER.Try d) of the previous post.
—> Standard setting after initial visio installation is “high”. “high” means that visio will prevent to execute not signed makros.
Hope this will help.
StephanPost Edited (09-03-04 10:45)
Andr,
Version 2.0 (available soon) will be able to export diagrams to XML.
Standard Edition (scheduled end of september, preview available in a few days) will support an export to a “simple XML” file.
BPEL export (also import) will be a feature of the Version 2.0, Professional Edition. Professional Edition is scheduled for 4Q04.
Hope this will help.
Stephan.Post Edited (08-23-04 23:35)
Pool and Lanes:
Yes, the Pool attribute in the lanes properties dialog is read only and will be set from Process Modeler automaticaly if you set the lane exactly into the pool. If the lane overlaps the pool border this attribute will be empty.
There is no way to expand automaticaly the size of Pools and Lanes if you add other elements (you have to do this manualy, but Visio is quiet cool to edit such things).The Business Transaction Flag indicates, that this activity will be run in a business transaction. This attribute will change in BPMN 1.0.
From BPMN 1.0 on only Sub-Processes can be transactional.
The specification will define the transaction attributes of a sub-process as follow:If the Transaction attribute is False, then a Transaction MUST NOT be identified. If the Transaction attribute is True, then a Transaction MUST be identified. The attributes of a Transaction can be found in the section entitled ‘Transaction’ on page 283. Note that Transactions that are in different Pools and are connected through Message Flow MUST have the same TransactionId.
Please compare for this the specification 0.9 and 1.0 final. 0.9 you can get from our web site and the 1.0 final you can download from bpmi.org.
-
AuthorPosts
