Hi all, I created a case say case #1 and displayed in bizagi suite. My requirement is to duplicate those case and make some minor changes and click submit,new case number should be created . Please suggest an idea.

Hi Team, I deleted some rows from Parameter entities table via SQL Server Delete script. All works fine in development, Metadata check is also fine but now when I try to do a advance deployment, it gives error while Creating import. It says "Finding deleted data in parameter entities. Integrity error found, fix them and repeat Export. " Please let me know how I can fix this? Is there any way I can get the values of parameter entities back? Attached the error while performing Process Import Analysis. See screenshot. Thanks, Swati

Is there a way to enter the text without space between lines for example text is "The task states are designated using three colors and is determined by the elapsed time taken from the moment the Activity was created coupled with the duration time defined for the task." in bizagi the text is entered as below "The task states are designated using three colors and is determined by the elapsed time taken from the moment the Activity was created coupled with the duration time defined for the task."

User wants to print the summary of the case and they also want to include comments section. how to get the comments as a printed format?

We have installed Bizagi 11 on "VMware app" volumes to attach to the desktop at login. so using the Bizagi installed on "VMware app" I am trying to connect the projects on another DEV Server. I have added the required credentials of users in "Bizagi" group of DEV Server, but we are getting error message "CCOnfiguration - Connection String not found in application setting". Can you please let us know as what are we missing on "VMWare". On the other hand, we can access DEV server project from Bizagi installed on our local machine without any issues. Only the problem is if we connect from "VMWare" machines. Please find attached screenshot of error message.

Hello. Whether saves bizag information on reassignment of a work item? It would be remarkable if we could obtain information: who has reassigned a task, to whom has been reassigned and when.

http://elearning.bizagi.com/pluginfile.php/13986/mod_resource/content/2/19_What%20is%20a%20timer/index.html in this link have a wrong video..

- When it’s a – (negative) value for any attribute in Bizagi, it shows it in brackets. For eg: -4 = (4) in Bizagi. However, we noticed negative values from -0.1 to -0.9 are not mentioned in brackets (). in case of negative percentages between 0 and -1% no brackets are put around the percentage value to indicate it is negative. S

I try to download saved Templates to use in Bizagi Studio , during the installation process in the wizard it gives the following err " no template found for project Database " after entering the credentials. Could Anyone please advise !?

When trying to create a new project, this appearing in the figure below, how to proceed in this case? Already I reinstalled about 3 times and nothing remains the same problem. Can someone help me?

hello, When we try to execute web service to our web service or to bizagi web service we get an error: "Could not generate proxy assembly for web service. Please check that Web Service exists and it is working: Could not find file 'C:\Bizagi\Projects\College\Temporary\SOA\SOAwwwbizagicom_ESB_ESBServicesasmx.cs'. Could not find file 'C:\Bizagi\Projects\College\Temporary\SOA\SOAwwwbizagicom_ESB_ESBServicesasmx.cs'" We already check: 1. Our network - no problem was found 2. We try another servers for WS includes bizagi WS and Local WS 3. We try to access from the web browser to WS servers and successful to do so 4. We try the WS methods and no problem was found 5. Checking the trace file - no file was found We will thanks for any help on this issue. Thanks, Nesi

Hello, When I try to create a new project, I get these errors: It was working before, but it suddenly stopped working. I haven"t changed anything in SQL server or any other configuration. I already Uninstalled and Installed the OperationServices again... Any help would be appreciated! Thanks!

Hi, I have followed your user guides for implementing the Bizagi web parts into SharePoint. Everything was successfully installed up until I try and set the connection for the web parts. When I navigate to the configuration list that has been created automatically and add a new list item I get the following message: The base type 'BizAgi.SharePoint.Layouts.Bizagi.SharePoint.EditPages.Bizagi_WebPartsConfigNewForm' is not allowed for this page. The type BizAgi.SharePoint.Layouts.Bizagi.SharePoint.EditPages.Bizagi_WebPartsConfigNewForm, Bizagi.SharePoint2013, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3cc953c7096d36f1 could not be found or it is not registered as safe. This means that I cannot create the connection that's needed. Many Thanks, Andy

I reinstalled my modeler but cannot get past the registration screen. It just hangs with a loading icon. I know my credentials are accepted because if I type in an incorrect password, I get an error message. How can I get past the product registration step?

Hi, I have Virtualized table/enity 'Customer ' which is mapped to External data source. Search for existing customer works fine through Bizagi form. But when I try to add new record in bizagi form, it doesn't allow to add new to Customer table in Bizagi. How can we add new record to Bizagi table which is Virtualized? Thanks,

Dear all, I'm setting up Bizagi Engine in Centos 7 . I have done already this steps: I have installed the JDK 1.6.45 (Oracle JDK, version 6, update 45). I have installed the JBOSS 6.2 GA web server and I have added the respective modules that are provided in the folder of BizAgi-ear-JBoss-dist-10.7.0.2255.rar. I have done all the tutorial of configuration of Bizagi Engine with JBOSS servers provided en your help: http://help.bizagi.com/bpmsuite/es/index.html?jee_jboss_deploy.htm. I have done the tasks "createproject" and "predeploy" with the consolemanager in order to get my "Portal Work" working. The problem happens when I try to run the file "BizAgi-ear-Jboss.ear" (generated into my "dist" folder inside of the folder of my project when I run the command predeploy) in my JBOSS server to get my "Portal Work" working. I put this file inside standadole/deployments of my JBOSS server then I run the "sh ./standalone" command to start my JBOSS server and I got the next error errors: 17:34:57,405 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commons-codec-1.7.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,417 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry joda-time-2.2.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xmlsec-1.5.6.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,742 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry slf4j-api-1.7.5.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,743 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry eclipselink-2.5.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,743 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry javax.persistence-2.1.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,743 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commonj.sdo-2.1.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,744 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry ojdbc6-11.1.0.6.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,744 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry sqljdbc-4.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,781 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commons-logging-1.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,782 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry logkit-1.0.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,782 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry avalon-framework-4.1.3.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,783 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry servlet-api-2.3.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,783 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commons-digester-1.8.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,790 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry javaee-api-5.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:34:57,810 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis.jar in /content/BizAgi-ear-JBoss.ear/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:57,881 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xercesImpl.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:57,881 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:57,881 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry serializer.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:57,900 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry activation.jar in /content/BizAgi-ear-JBoss.ear/mail-1.4.jar does not point to a valid jar for a Class-Path reference. 17:34:58,276 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis.jar in /content/BizAgi-ear-JBoss.ear/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:58,277 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xercesImpl.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:58,278 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:58,278 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry serializer.jar in /content/BizAgi-ear-JBoss.ear/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 17:34:58,336 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "BizAgi-war.war") 17:34:58,337 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "BizAgi-ejb.jar") 17:34:58,336 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "null" (runtime-name: "bizagi-scheduler.jar") 17:34:58,360 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry cmis10-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,360 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry vision-da-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,361 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry common-base-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,361 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry togglz-slf4j-2.0.1.Final.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,364 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry bcpg-jdk15on-1.50.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,365 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry bcprov-jdk15on-1.50.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,365 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,365 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry entities-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,366 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry localization-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,366 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry content-manager-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,366 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry entity-manager-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry single-sign-on-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-httpclient-3.1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,421 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry metadata-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry bizagi-remote-2.0.6.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry baas-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry mapping-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry integration-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry sap-jco-3.0.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry integration-external-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry query-engine-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry wfes-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry bl-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry analysis-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry render-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry web-services-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry ui-ajax-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry render-aspx-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry business-logic-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry archiving-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry job-manager-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:34:58,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry bizagi-web-10.7.0.2255-def.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:35:01,382 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry eclipselink-2.5.0.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:35:01,383 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry javax.persistence-2.1.0.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:35:01,383 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commonj.sdo-2.1.1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:35:01,383 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry sqljdbc-4.0.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar does not point to a valid jar for a Class-Path reference. 17:35:02,515 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry activation.jar in /content/BizAgi-ear-JBoss.ear/mail-1.4.jar does not point to a valid jar for a Class-Path reference. 17:35:02,527 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-codec-1.7.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,527 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry joda-time-2.2.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,527 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xmlsec-1.5.6.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,528 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry slf4j-api-1.7.5.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,528 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry eclipselink-2.5.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,528 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry javax.persistence-2.1.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,528 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commonj.sdo-2.1.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,529 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry ojdbc6-11.1.0.6.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,529 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry sqljdbc-4.0.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,529 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-logging-1.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,529 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry logkit-1.0.1.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,530 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry avalon-framework-4.1.3.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,530 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry servlet-api-2.3.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,530 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-digester-1.8.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,531 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry javaee-api-5.jar in /content/BizAgi-ear-JBoss.ear/saml-configuration-10.7.0-SNAPSHOT.jar does not point to a valid jar for a Class-Path reference. 17:35:02,542 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry bizagi-web-10.7.0.2255-dist.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jersey-server-1.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry asm-3.1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,551 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jersey-core-1.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,551 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jsr311-api-1.1.1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,551 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jersey-multipart-1.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,551 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry mimepull-1.4.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,552 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jersey-client-1.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,552 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry build-tools-1.0.5.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,552 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jmimemagic-0.1.2.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,552 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry oro-2.0.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,553 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry xmlParserAPIs-2.0.2.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,553 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry workportal-services-10.7.0-SNAPSHOT.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,553 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry tomahawk-1.1.9.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,553 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry commons-validator-1.3.1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry commons-el-1.0.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry batik-awt-util-1.6-1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry batik-util-1.6-1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry batik-gui-util-1.6-1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry batik-ext-1.6-1.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry itext-1.4.8.jar in /content/BizAgi-ear-JBoss.ear/BizAgi-war.war does not point to a valid jar for a Class-Path reference. 17:35:02,717 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."BizAgi-ear-JBoss.ear"."BizAgi-ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."BizAgi-ear-JBoss.ear"."BizAgi-ejb.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "BizAgi-ejb.jar" of deployment "BizAgi-ear-JBoss.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:448) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:270) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:152) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:80) at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58) at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] ... 5 more 17:35:02,799 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,800 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,800 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,800 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,801 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,801 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,801 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,801 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,802 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,802 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,802 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,803 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,803 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,803 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 17:35:02,805 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,805 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,805 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,805 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,807 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,807 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter' 17:35:02,808 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:02,809 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:02,809 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:02,809 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:02,809 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:02,810 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider' 17:35:03,025 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"BizAgi-ear-JBoss.ear\".\"BizAgi-ejb.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"BizAgi-ear-JBoss.ear\".\"BizAgi-ejb.jar\".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment \"BizAgi-ejb.jar\" of deployment \"BizAgi-ear-JBoss.ear\" Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}} 17:35:03,037 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: bizagi-scheduler.jar) in 11ms 17:35:03,040 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: BizAgi-ejb.jar) in 14ms 17:35:03,611 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: BizAgi-war.war) in 584ms 17:35:03,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear (runtime-name: BizAgi-ear-JBoss.ear) in 679ms Even, I have copied the .orig file, I have configured the enviorenment variables and I have copied the modules inside modules folder oF JBOSS Server. PD: As additional information I have to say that I`m doing all in an standalone JBOSS configuration, using an Oracle 11gR2 database and using the BizAgi-ear-JBoss-dist-10.7.0.2255.rar. provided in the last update. I will add the ouput that I get when I run the command: sudo ./standalone.sh to start the JBOSS Server. Regards and thanks in advance.

Hola, Tengo un problema al ejecutar el portal, no me aparecen algunos procesos, solo aparecen algunos y no se como hacer para que puedan ser visibles la totalidad de todos mis procesos. Espero me puedan ayudar. Gracias.

Hello Again. I want to get the values from a collection that i got using CEntityManager.GetEntity: I need to obtain the "CurrentRecluited" attrib Value but it gives me error. How can i get that value?.

I had to re-install the software and not cannot re-register the product. It appears to validate my password because it knows if type an invalid password. But the sign In window hangs showing the loading icon. How can I get by this step.

Hi, Did the virtualization between Bizagi table and external data source (here used SQL). For example taken Department table (Department ID, Name, DepartmentGroupName). The Data Virtualization Entity and attribute were created without any issues. Am using the Department as part of the search in Bizagi form based o\in DepartmentID. The search retrieves the right record from External Database and displays in the form (which eventually saved to Bizagi Database). Here I face an issue when I got to Modules (Expert in Bizagi 11) view, and go to Enitites --> Master --> Department --> Values, then it pulls all the records from External Database to Bizagi Database. Is this can be controlled? Thanks. Neel