Shark - Java Open Source XPDL Workflow Activity
Brought to you by:
a_madl
Activity for Shark - Java Open Source XPDL Workflow
-
Sasa Bojanic posted a comment on discussion Open Discussion
Hi Allen, I think you can find it in documentation...default username/password to log-in should be admin/enhydra Greetings, Sasa.
-
Allen posted a comment on discussion Open Discussion
Hi, I installed tws 6.5.2. But I don't know how to login to the server and web client.
-
Rezan Kedik modified a comment on discussion Open Discussion
Hello everybody, in the moment i am writing my bachelor thesis on the topic "Diffusion rate of open source business software". I want to ask you (the Community) who is using and/or supporting the Software "Shark-Java Open Source XPDL Workflow", if you would conduct the quick survey, based on the software "Shark-Java Open Source XPDL Workflow". Under the following link, you can start with these: https://www.umfrageonline.com/s/8b5eeb1 I would be very grateful, if you could take the time and conduct...
-
Hello everybody, in the moment i am writing my bachelor thesis on the topic "Diffusion rate of open source business software". I want to ask you (the Community) who is using and/or supporting the Software "Shark-Java Open Source XPDL Workflow", if you would conduct the quick survey, based on the software "Shark-Java Open Source XPDL Workflow". Under the following link, you can start with these: https://www.umfrageonline.com/s/54e5d89 I would be very grateful, if you could take the time and conduct...
-
-
# Manually updated components from automatic build
-
# Updates related to the creation of new 6.5-5 branch
-
-
-
-
-
# Updated includes file before tagging
-
# Manually updated sources from the BUILD2
-
# Update due to the new 6.5-4 branch
-
-
-
-
# Preparing for the branch release
-
# Preparing for the branch release
-
# Prepared 6.5-3 branch
-
-
-
Hi, a new version of Enhydra Shark is released and available for download from https://sourceforge.net/projects/sharkwf/files/shark/6.5-2 Main changes since version 6.4-4: SMTP related Plugins (SMTPDeadlineHandler, SMTPErrorHandler, SMTPEventAuditManager) now support sending of signed emails Improved DefaultMailMessageHandler and MailToolAgent to be able to send signed emails (without usage of SMIMEMailMessageHandler) Fixed deadline checking in DODSPersistentManager. Now the SQL query in getAllIdsForProcessesWithExpiriedDeadlines()...
-
Hi, a new version of Enhydra Shark is released and available for download from https://sourceforge.net/projects/sharkwf/files/shark/6.5-2 Main changes since version 6.4-4: SMTP related Plugins (SMTPDeadlineHandler, SMTPErrorHandler, SMTPEventAuditManager) now support sending of signed emails Improved DefaultMailMessageHandler and MailToolAgent to be able to send signed emails (without usage of SMIMEMailMessageHandler) Fixed deadline checking in DODSPersistentManager. Now the SQL query in getAllIdsForProcessesWithExpiriedDeadlines()...
-
Shark - Java Open Source XPDL Workflow released /shark/6.5-2/tws-6.5-2.zip
-
-
-
-
-
-
-
-
-
# Manually propagating TAB build dependencies
-
# Updated language components (extended with new entries required by TDM/TTM)
-
-
-
# Changes due to the version number increase
-
-
-
# Manually propagating TAB build dependencies
-
-
# Manually propagating TAB build dependencies
-
# Supported filtering of the worklist by Subject and Description
-
# Supported filtering of the worklist by Subject and Description
-
-
-
# Now SETUP EXE also deploys WebClient on Tomcat
-
-
# Manually propagating TAB build dependencies
-
# WebService implementation improved to be able to configure default UserTransaction timeout
-
# Updated release notes
-
# Improvement for sending signed emails without attachment (issue with UTF characters)
-
# ComponentIncludes.csv - corrected include for bcmail component
-
# Updated release notes
-
# Updated release notes
-
# SMTPDeadlineHandler improvement
-
# Manually propagating TAB build dependencies
-
# Build improved to include bcmail.jar in all the distribution packages
-
# Improved DefaultMailMessageHandler and MailToolAgent to be able to send signed emails (without usage of SMIMEMailMessageHandler)
-
# Manually propagating TAB build dependencies
-
# Manually propagating TAB Build dependencies
-
# StandardAssignmentManager plug-in now also defaults to system configuration "StandardAssignmentManager.appendResponsibles" if extended attribute
-
Tecnoteca srl posted a comment on discussion Open Discussion
Dear Sasa, we are advancing a process in this way: wapi.changeActivityInstanceState(handle, procInstId, actInstId, WMActivityInstanceState.OPEN_RUNNING); ... wapi.changeActivityInstanceState(handle, procInstId, actInstId, WMActivityInstanceState.CLOSED_COMPLETED); where wapi = SharkInterfaceWrapper.getShark().getWAPIConnection(); We also start a connection in this way: WMConnectInfo wmci = new WMConnectInfo(username, password, DEFAULT_ENGINE_NAME, DEFAULT_SCOPE); wapi.connect(wmci) How can we configure...
-
# SMTP related Plugins (SMTPDeadlineHandler, SMTPErrorHandler, SMTPEventAuditManager) modified to read the information about email signing from the configuration
-
# Improved documentation for deploying on Tomcat
-
# Changes due to the creation of the new branch
-
-
-
Hi, the persistence layer has the configuration for the transaction timeout...however, by default it is set to 5mins (normally set in SharkClient.conf, property UserTransaction.Timeout) Regarding WebService timeout, I think it is up to your client application to define the timeout... Regards, Sasa.
-
Hi, There is no easy way to do it. You would have to migrate DB data. The following columns should be migrated in the "runtime" tables: SHKProcesses: ProcessDefinition, PDefName SHKActivity: PDefName SHKAssignmentsTable: ActivityProcessDefName The following columns should be migrated in the "reporting" event audit tables (if used): SHKActivityHistoryInfo: ProcessFactoryName, ProcessFactoryVersion, ProcessDefinitionId SHKProcessHistoryInfo: ProcessFactoryName, ProcessFactoryVersion, ProcessDefinitionId...
-
Hi all, we are using version 4.4-1 through SOAP web services and we are experiencing timeout errors for operations longer that 1 minute. It seems more an error of web service component than the persistence one, is there a way for configuring them both? Best regards.
-
-
# Manually propagating TAB build dependencies
-
# Build updated to support path with Whitespace
-
# Build procedure modified to support white-spaces in the path
-
tkofford posted a comment on discussion Open Discussion
I have a situation where we have 3 process definitions in 3 different package (XPDL) files. After some time, we consolidated those 3 process definitions into a single, new package (XPDL) file. Our application is processing process instances from the old packages and new package, but only instantiates new processes from the new package. So we have a mix of process definitions from the 3 old packages, and the 1 new package. Is there an easy way to move/migrate the instantiated processes from the old...
-
# Build changed to support source folder have whitespace character in its name
-
# New branch 6.4-6 synchronized with the following trunk changes:
-
# Changes due to new 6.4-6 branch
-
-
-
# SMTP related Plugins (SMTPDeadlineHandler, SM...
-
# NSI file changed so that configuration dialog...
-
# Fixed build procedure so that project name ca...
-
# Now tws-x.y-z.datalayer.zip file has structur...
-
# Manually propagating TAB build dependencies
-
-
# Updating language file and fixing the build p...
-
# Manually propagating TAB build dependencies
-
# Manually propagating TAB build dependencies
-
# Updated language files from TLM
-
# Manually propagated TAB build dependencies
-
# Manually propagated TAB build dependencies
-
# Manually propagated TAB build dependencies
-
Assignment is represented through WMWorkItem or WfAssignment object in Shark's API...
-
# SWC: HTTPURLAPIUtils - Now deleting/terminati...
-
I have multiple applications using a single instance of shark/TWS, which each application...
-
# Synchronizing branch with "sending signed ema...
-
# Updated SWC changelog
1 >
