function thread(threadid, title, poster, threaddate, threadtime, message, postid) { this.threadid = threadid; this.title = title; this.poster = poster; this.threaddate = threaddate; this.threadtime = threadtime; // Post object, contains the post data this.post = new post(message, postid); } // This function is used to show the posts of the thread. function post(message, postid) { this.postid = postid; this.message = message; } var threads = new Array(15); threads[0] = new thread(5618117, 'XPDL Export', 'anagha', 'Dec 12, 2011', '07:32 AM','Hi
I am trying to export my business process diagram in XPDl format,but while doing this properties of Activities(Tasks) like attached Deliverables or associations does not get exported in XPDL file.
Can anyone suggest a way to get those properties in XPDL please ?
','1271372261'); threads[1] = new thread(5303314, 'Strategy Implementation', 'billaronson', 'May 28, 2011', '11:46 PM','Apart from the technical issues of usIng ProVision what about the strategy? How do you get buy in? How do you manage up?

Packt have just published my book on the subject and you can read a free chapter at http://tinyurl.com/OpenText1 (no login or requirements to give email address). Here\'s what some people are saying:

It’s the first book ever published on ProVision® that focuses on how to design a strategy and get it implemented.
Tom Foster - Owner, Business Views LLC

A blueprint for designing an organization that is truly customer centric.
Ray Brown - founder ClienteerHub.com

Moves you beyond the "red ocean" of survival and into the "blue ocean" of abundance.
Jeremy Scrivens - founder TheEmotionalEconomy.com

Will fast track your ability to get the most from ProVision® . Highly recommended.
Andrew Mackenzie - CEO Shirlaws.com.au

You can find out more at:
http://www.packtpub.com/metastorm-provision-62-strategy-implementation/book

Bill Aronson
','1268793051'); threads[2] = new thread(5074648, 'Verg urgent opening for Metastorm Programmer', 'chaku11483', 'Feb 02, 2011', '11:34 AM','

Hi,

Greeting from Ascenders HRO Team!

Apologies in advance if this mail has caused any inconvenience to you. Kindly refer your friends if you are not interested for below opening

Not wanting to disturb you by calling, thought to mail you my views first for your consideration. If interested and confident, please mail me your up-dated CV to Chakravarthy@ascenderstech.com with current and expected CTC, Notice period and call me directly / inform me your convenient time to call you before we have a F2F meeting to take this forward.

Company Name: Ascenders Technologies Pvt Ltd
Work Location: ON SITE
Skill Set: Metastorm Programmer
Experience: 3 - 6 years

Job Description:
• Min 2+yrs of experience in Metastorm programming or development.
• Strong Experience in development of C#.
• Strong Experience in development of .Net.
• Should have excellent communication.
• Should hold valid Passport

Wishing you all the very best in whatever you do.

Regards,
Chakravarthy
Mobile: +91-9500053834
Sr. Recruiter - HRO | Ascenders Technologies Private Limited

','1267106119'); threads[3] = new thread(4831416, 'inbound/outbound issue', 'laustu', 'Aug 05, 2010', '09:07 AM','Dears,

I would like to confront you guys with an major problem I have concerning the publishing of workflow models.

I have created different workflow models which contain general activities. These general activities group a set of specific activities, which I have put in a new workflow model and attached to its general activity.

When I open the workflow model, attached behind a general activity, I can see the in & outbound activities. But when I publish my repository to HTML, I can not see these in & outbound activities anymore. This is pretty unpleasant since it prohibits to see how some activities are triggered.

Can anyone help me out ?

Thanks in advance,

Laurens
','41323013'); threads[4] = new thread(4714010, 'How to rotate a text box', 'scaigs', 'May 12, 2010', '01:36 PM','Good morning,

I am looking to rotate freely a text box so the text can follow the line connector between two objects.

Please advice,

Luis
','40208002'); threads[5] = new thread(4686547, 'Can we setup provision repository on MS SQL database', 'andri_as', 'April 23, 2010', '08:10 AM','Dear All,

Can Provision create repository using MS SQL database? because I see the script file on creation of PVW database (createpvwdb.sql). I\'m using Provision 6.2.1.
Anyone know how to connect provision with that sql database?

Thanks,
Andri

','39933160'); threads[6] = new thread(4656497, '*.dot templates', 'Anna', 'April 02, 2010', '10:58 AM','Hi, everybody!
Please help to understand how to create a customized .dot template. I tried to change a standard template (delete some bookmarks), but received no result.
Can you recommend some documantation?
Thank\'s!
','39621255'); threads[7] = new thread(4604128, 'Formatting', 'guenzbub', 'Feb 26, 2010', '09:43 AM','

How can I apply minimal formatting in a description of an object (eg system), like lists, bold text, a bit like the bar that is seen when creating this message.

','39092181'); threads[8] = new thread(4488385, 'BridgeStart / BridgeEnd - Jump feature', 'xanthia', 'Feb 02, 2010', '03:15 PM','Hi,

I am new to Metastorm Provision so I will be asking possibly a very simple question that I need help on.

I created a BridgeStart and a BridgeEnd by just placing it within my buiness process workflow model.

Now the 2 questions I have are:
1) How can I label the BridgeStart and BridgeEnd with number identifiers?
2) How can I use the jump feature to show that this BridgeStart is linked with this BridgeEnd when you click on it....

I am using Provision v6.1.4.

Thank you so much for taking the time to read this and especially if you can help me out.

Sincerely,
Xanthia
','38584035'); threads[9] = new thread(3605005, 'Importing Visio diagrams', 'grayoron', 'Aug 05, 2009', '01:19 PM','How do you import Visio diagrams and is there a list of Visio shapes mapped to ProVision objects?

Here is what I have found so far:
The Visio Exchange function provides a direct interface with Visio. This interface makes it possible to populate Metastorm ProVision models from Visio diagrams.

Since Visio is a diagramming tool, not a modeler, its objects do not carry significant meaning. This requires the user to be more actively involved in mapping Visio objects into Metastorm ProVision objects. The mapping is accomplished in three key steps:

Select Source and Target: Visio Exchange will ask the user to select a Visio diagram and then select how the diagram is to be interpreted. In effect, it asks the user to select a Metastorm ProVision modeler to map the diagram into.
Map Objects: Visio Exchange will map the diagram objects into the objects which apply in the selected modeler. This detailed object-by-object mapping is then presented to the user. This saves the user from mapping each object one-by-one.
Refine Mapping: The user may now go through each mapping decision an object-by-object basis.

','34776176'); threads[10] = new thread(2268481, 'Resolved Issues in ProVision V6.0.2', 'Admin', 'Nov 04, 2007', '02:51 AM','

Support Case ID Resolution
3571, 12744 Publishing to Word no longer truncates text for a Bridge start/end object.
9353 Attempting to publish a deleted model no longer causes an abnormal termination.
11881 For all model zoom levels, the correct artifact will display when selected.
11970 A custom object in a model that has two different contexts in Workflow Models no longer refreshes repeatedly.
12061 All Property Grid columns can now be resized.
12246 Trailing spaces are not allowed in object names.
12281, 13225 The characteristic link between the message and service operation now shows in the Navigator model.
12306 Context objects not displaying under certain conditions has been corrected.
12352 A typo was corrected in the Import Provision Objects dialog.
12427 Translator now imports Stereotype values correctly (non-zero).
12530 An Association moved from one connector to another now retains the new connection.
12642 The default value for a custom property in the Customization Control Panel can now be removed.
12722, 12856 In the process model interpretation, component objects are now sequenced in numerical order.
12814 Copying the contents of a Workflow Model that includes a custom link no longer causes an abnormal termination.
12826 A layered Sequence Model no longer loses links when opened and closed.
12832 Properties of a finalized activity will no longer be modifiable in the activity usage dialog.
12846 A typo in the Model Detail Page tab has been corrected.
12961 Importing dimensions of the same name, but different types via Translator is now supported.
13085 Customized links no longer disappear under certain conditions.
13107 Objects that had been rotated were causing abnormal termination when copied; this has been corrected.
13108 An incorrect error message for adding new Business Processes has been fixed.
13108 An incorrect error message when renaming Business Domains has been fixed.
13159 Custom links can no longer appear between workflow lanes and activities.
13202 Transit times in workflows are no longer reset to zero when you close the dialog.
13212 Child folders are no longer deleted incorrectly in Property View.
13235 In the Sequence Model, numbers will display on operation objects and the number will be used in the interpretation sort order.
13236 Right clicking on the Index bar displays the appropriate context menu.
13241 Exporting a gallery and importing its objects into another gallery now updates the objects instead of adding.
13248 A Where Used grid cannot be created without tick marks.
13264 An Activity association now displays in the Artifact dialog.
13313 The drill-down indicator no longer shows for objects that are not the subject of any model.
13384 Power Add no longer creates duplicate objects in Object Inventory.
- The Publisher no longer allows the creation of a new publish list without a name definition.
- Activity usage properties such as resources are copied when a substitution is performed.
- Adherence and custom links to the same Rule object can now be disassociated.
- Double clicking the name of an object in an association grid now brings up the Details dialog.
- A text truncation issue has been resolved in the Import Objects dialog.
- Role text is no longer reversed in an association grid.
- Objects in the Navigator now show their names with Packages.
- Association Grids now show Packages, Classes and Interfaces with their Package Namespaces.
- Substituting a projection for an object no longer drops operations on its stem.
- Opening and closing a Property Grid in a notebook seen in Explorer View no longer causes abnormal termination.
- Opening and closing a Property Grid in the Process category seen in Explorer View no longer deletes the grid.
- A custom default modeling language imported through a new repository is now retained correctly.
- A CRUD bookmark has been added to the business class template file.
- The check box object size (for new objects) string is no longer truncated when the Revert to Defaults option is used.
- Running Discrete Event Simulation and Monte Carlo Simulation on a workflow model now creates valid Activity State Charts.
- Renamed clone projections are now differentiated from the original clone.
- A typo has been corrected in the System Data Exchange Object dialog, Properties tab, Protection Duration dropdown list.
- An �invalid argument� error in exporting to BizTalk has been corrected.
- In customization, updating the style of business domains will no longer update the activity style.
- A minor HTML formatting issue was corrected.
- Files are no longer deleted if a checkin fails.
- A linked custom Property is now generated correctly when published to HTML.

','21606306'); threads[11] = new thread(2268478, 'Enhancements in ProVision V 6.0.2', 'Admin', 'Nov 04, 2007', '02:49 AM','

Support Case ID         Enhancement
12294         Linux and UNIX path naming conventions are now supported for images.
12802         Custom links are now available in association and property grids, regardless of their membership in a model
-         The Modeling Language Import dialog now allows users to specify the desired handling of data type collisions.
-         Toolbar settings are now retained after an uninstall of a previous version of ProVision.
-         XPDL export is now supported.
-         BPEL support has been added for Microsoft BizTalk and WebSphere Integration Developer.
-         Microsoft Word 2007 and Excel 2007 formats are now supported by Translator.

','21606283'); threads[12] = new thread(2232330, 'Top 10 reasons to use Metastorm ProVision for Requirements Analysis', 'Admin', 'Oct 19, 2007', '01:08 AM','Requirements Analysis

Getting the Requirements Right

Failure to obtain accurate and complete business requirements has long been the sour note of application development. Lack of communication between the developers and business users leads to more project failures than any other single cause. Metastorm\'s model driven solution for requirements analysis can change that.

Metastorm ProVision® enables business and IT teams to establish consensus on how business processes should work, which business processes are best served through automation, and how technology will support those business processes. It includes detailed business models that eliminate ambiguity and provide a clear, detailed definition of business requirements. The resulting model-based deliverables are a reliable basis for designing an automated solution.

Before your organization launches its next package selection, implementation or upgrade, make sure you identify the right requirements. Metastorm ProVision will significantly reduce requirement errors and thus improve software quality.
Who does Requirements Analysis?

    * System Engineers
    * Business Analysts



    * Developers
    * Project Leaders



    * Product Managers
    * Design Engineers

Top 10 reasons to use Metastorm ProVision for Requirements Analysis:

   1. No requirements modeling tool is easier to use! Your requirements modeling tool most likely will be used by the same analysts who use MS Office. Metastorm ProVision was designed to be intuitive for MS Office users. The portal, a powerful and easy-to-use graphical user interface for Metastorm ProVision, provides an intuitive way to graphically model and gather requirements from multiple perspectives.

   2. Metastorm ProVision models provide the most effective method for gathering, visualizing and analyzing business requirements. This is further enhanced by Metastorm ProVision\'s ability to manage objects across models and create associations between various object types. Powerful association matrices can also display and manipulate associations between any two object types.

   3. With Metastorm ProVision you see the big picture. You can define and analyze the entire requirements business domain. Metastorm ProVision contains a powerful “interpreter” which translates any model into simple English at the click of a mouse.

   4. Put your requirements in class by themselves. Metastorm ProVision describes the information for a given business domain as a set of business classes. Using the Business Class Model these classes can be structured into a representation of how they fit relative to other classes in the domain. The Business Class Model also shows the three types of properties for each business class: its associations, attributes, and operations.

   5. Just identifying the information is not enough. An understanding of the changes that business undergoes requires a Statechart Model. With the Statechart Model an analyst can focus on a particular business class and illustrate its lifecycle. The Statechart Model allows an analyst to depict the major stages (states) that an instance of the business class can experience, the allowable transitions between states, and the operations that transition the instance from state to state.

   6. Tie information changes to business activities. Metastorm ProVision can define operations that bring about the state changes related to a business class. This provides analysts with the ability to link operations associated with each class directly to one or more activities, or link multiple business classes to a single activity through a sequence model, which describes a series of operations across of classes.

   7. Automation is the key. Business activities described in Metastorm ProVision can be extended to show the specific user interfaces required to access a proposed system as well as the navigation between them. These user interfaces can also be extended to show interface mockups or images of the actual interfaces to assist in system design and documentation. Interfaces between systems can also be described using the communication model.

   8. Flexibility as a rule. By using the rule object and model, business rules can be captured, organized and associated with any Metastorm ProVision object.

   9. Put your requirements on a firm foundation. Metastorm ProVision provides an instrument to define and model requirements related to infrastructure components in the form of facilities, equipment and technologies.

10. The key factor in assuring requirement accuracy is visibility. Metastorm ProVision models and interpretations can be published as HTML files that can be viewed interactively by all team members. The information captured in Metastorm ProVision can also be used to facilitate training during implementation.

','21247550'); threads[13] = new thread(2180622, ' Share your Models', 'Admin', 'Sept 26, 2007', '08:38 AM','

Share your Models

Metastorm ProVision allows you to import and export business and UML/object models with other popular tools. New Data Exchange modules can be developed easily using the Metastorm ProVision open API based on MS COM (Component Object Model) or XML.

Metastorm ProVision currently supports the following Data Exchanges:
(Some interfaces are not available in the Process edition.)

BPEL
Business Process Execution Language (BPEL) for Web services is an XML-based language designed to enable task-sharing in a distributed computing environment (including multiple organizations) using a combination of Web services. Using BPEL, a developer formally describes how a business process will take place so that any other cooperating organization can perform one or more steps in the process the same way. Using a supply chain process as an example, BPEL might be used to describe the protocol of information comprising a product order, as well as the exceptions that may arise.
Translator
Metastorm ProVision includes a Translator, which enables you to export or import notebook contents (including objects and their properties, if applicable) in any of the following formats: MS Excel (form or tabular format) MS Word (form or tabular format) Comma-separated format (.csv or tabular format) XML (tabular format) With Metastorm ProVision you can export object information to a formatted table with no specific data (only template headings for the object and property types), or in a file populated with the objects and properties you selected. You can import tabular-formatted object information or choose to place the imported data in a specific model or into inventory, which enables you to use it in whatever models/objects you choose.
VisioExchange
The Visio Exchange function provides a direct interface with Visio. This interface makes it possible to populate Metastorm ProVision models from Visio diagrams. Since Visio is a diagramming tool, not a modeler, its objects do not carry significant meaning. This requires the user to be more actively involved in mapping Visio objects into Metastorm ProVision objects. The mapping is accomplished in three key steps: Select Source and Target: Visio Exchange will ask the user to select a Visio diagram and then select how the diagram is to be interpreted. In effect, it asks the user to select a Metastorm ProVision modeler to map the diagram into. Map Objects: Visio Exchange will map the diagram objects into the objects which apply in the selected modeler. This detailed object-by-object mapping is then presented to the user. This saves the user from mapping each object one-by-one. Refine Mapping: The user may now go through each mapping decision and modify on an object-by-object basis. This provides the user object-by-object
RoseExchange
The Rose Exchange function provides a direct interface with Rational Rose. This interface makes it possible to populate Metastorm ProVision from Rational Rose and, similarly, to populate Rational Rose from Metastorm ProVision. The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and Rational Rose. It consists of two major functions: Import enables the more technical objects expressed by Rose to be incorporated into the more business-like repository of Metastorm ProVision. This provides, among other things, a way to use Rose data as the seed for developing robust business models. Export enables Metastorm ProVision to be used as a source for populating Rose diagrams. One very common use of Export is as part of a lifecycle handoff. Business and Analytical models developed in ProVision can be exported to Rose for technical development (detailed design and code generation). These capabilities are all accomplished by the Rose Exchange function. These capabilities are all accomplished by the Rose Exchange function.
*Together*
The Together Exchange function provides a direct interface with Together. This interface makes it possible to populate Metastorm ProVision from Together and, similarly, to populate Together from Metastorm ProVision.
ERwinExchange
The ERwin Exchange function provides a direct interface with ERwin. This interface makes it possible to populate Metastorm ProVision from ERwin and, similarly, to populate ERwin from Metastorm ProVision. The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and ERwin. It consists of two major functions: Import enables the more technical objects expressed by ERwin to be incorporated into the more business-like repository of Metastorm ProVision. This provides, among other things, a way to use ERwin data as the seed for developing robust business models. Export enables Metastorm ProVision to be used a source for populating ERwin diagrams. One very common use of Export is as part of a lifecycle handoff. Business and Analytical models developed in Metastorm ProVision can be exported to ERwin for technical development (detailed design and code generation). These capabilities are all accomplished by the ERwin Exchange function.
MSProjectExchange
The benefits of the MS Project Exchange applies when the user has built workflow models that express (conceptually) tasks and dependencies. The MS Project Exchange will automatically populate MS Project and enable the full functionality of that tool to be applied. The Exchange includes tasks (activities), dependencies (workflow links), cost and timing information and resource utilization.
DDLExchange
The DDL Exchange function provides an interface with most relational database management systems that meet ANSI/ISO SQL 92 standards. This interface makes it possible to populate Metastorm ProVision from DDL scripts and, similarly, to generate DDL scripts from Metastorm ProVision. The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and DDL. It consists of two major functions: Generation enables Metastorm ProVision to be used as a source for generating database schema in the form of DDL scripts Reverse engineering enables database schema in the form of DDL scripts to be brought into Metastorm ProVision to be represented as object models. These capabilities are all accomplished by the DDL Exchange function.
C++
The C++ exchange function enables you to specify the design options for generating C++ components from class model components.
XMI
The XMI Exchange function uses XML Metadata Interchange (XMI) to interface with other business modeling and reporting tools via Extended Markup Language (XML). This makes it possible to populate Metastorm ProVision from such external software that recognizes the XML format and to populate the software from Metastorm ProVision.

','20723858'); threads[14] = new thread(2180612, 'BPA Modelers', 'Admin', 'Sept 26, 2007', '08:23 AM',' Metastorm ProVision® Modelers Optimize Results

The modelers of Metastorm ProVision for Business Process Analysis provide process and organizational mapping capabilities for documenting and analyzing your business processes and organizational interactions. All business and process models from Metastorm ProVisionBPA can be used in Metastorm ProVision for Enterprise Architecture for further analysis and development.

BPA Modelers
Process Motivation	Process Definition
Strategy Modeler Goal Modeler Problem Modeler Opportunity Modeler Impact Modeler	Workflow Modeler Process Modeler Rule Modeler Deliverable Modeler
Process Participation	Process Analysis
Business Interaction Modeler Communication Modeler Organization Modeler Location Modeler System Modeler	Timing Analysis Cost Analysis State Analysis

','20723807');