Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionsession roles will be no longer supported in future. use
SessionChooser.anonymous().session roles will be no longer supported in future. useSessionChooser.anonymous().session roles will be no longer supported in future. useSubSessionChooser.anonymous().session roles will be no longer supported in future. useSubSessionChooser.anonymous().useBusinessDataRepository.current()insteaduseICaseMapService.current()insteaduse insteadVariables.names()not supported anymore. always returns empty string.WebPage features was removed with 11.2. Use HtmlDialog instead.this feature is moved to the engine cockpit.useLazyDataModel. Primefaces has changed this interface in version 10 and 11.useIvyFreyaThemeuseSubProcessCallStartandSubProcessCallinsteadinstead useSubProcessCallinstead useSubProcessCalland @{linkSubProcessCallStart.call(Object...)instead useSubProcessCalland @{linkSubProcessCallStart.call(Object...)instead useSubProcessCall,SubProcessCallStartParam.withParam(String, Object), and @{linkSubProcessCallStart.call(Object...)instead useSubProcessCallStart.find(SubProcessSearchFilter)useSubProcessSearchFilter.Builder.setSearchScope(SearchScope)with parameterSubProcessSearchFilter.SearchScope.APPLICATIONorSubProcessSearchFilter.SearchScope.PROJECT_AND_ALL_REQUIREDuseSubProcessSearchFilter.Builder.setSearchScope(SearchScope)with parameterSubProcessSearchFilter.SearchScope.PROJECT_AND_ALL_REQUIREDorSubProcessSearchFilter.SearchScope.PROJECTUsech.ivyteam.ivy.bpm.exec.IBpmnProcessElementinstead.useAbstractProcessStartEventBean.getConfig()instead.instead useIProcessStartEventBeanRuntime.processStarter()directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)ch.ivyteam.ivy.process.extension.ICommonProcessExtensionConfigurationEditor.setConfiguration(String) directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)useAbstractProcessExtension.getConfig()insteaduseAbstractProcessExtension.getConfig()instead.directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)IProcessExtension.setConfiguration(ProgramConfig)is used instead.useExtensionUiBuilder.scriptField(String)instead.useExtensionUiBuilder.scriptField(String)instead.no use-case with web-based inscriptionno use-case with web-based inscriptionuseAbstractProcessIntermediateEventBean.getConfig()insteaduseISecurityMember.getSecurityMemberId()session roles are no longer supported. useISecurityMember.isMember(IUserToken)session role is no longer supported. assign roles to user.grouping by identifier makes no senseisGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.not used anymore. cases which become zombies will be deleted.UseIDocument.uuid()Attention: YOU SHOULD NOT USE THIS. If you use an external document provider like S3, documents are not available on the local file system, therefore the files needs and will be automatically cached on the local system. Always prefer using the following methods in the given order: -IDocumentContentReader.asStream()-IDocumentContentReader.asReader()-IDocumentContentReader.asBinary()-IDocumentContentReader.asString()If you like to pass a document for example as Mail attachment, then simply use the document directly, becauseIDocumentextendsDataStreamProvider.Attention: YOU SHOULD NOT USE THIS. If you use an external document provider like S3, documents are not available on the local file system, therefore the files needs and will be automatically cached on the local system. Always prefer using the following methods in the given order: -IDocumentContentReader.asStream()-IDocumentContentReader.asReader()-IDocumentContentReader.asBinary()-IDocumentContentReader.asString()If you like to pass a document for example as Mail attachment, then simply use the document directly, becauseIDocumentextendsDataStreamProvider.Use get(StrinuseICase.tasks().allActive()Returns all active child tasks.useICase.owners(). A case can have multiple owners. This will return only one owner. Returns the owner of the case. Maybe null if no owner was set withICase.setOwner(ISecurityMember).
The intend of the owner is only for descriptive purpose and has no influence on the behavior of the Workflow Engine. This may can be used for example in Workflow UIs to search and filter in case lists.useICase.owners(). A case can have multiple owners. This will return only the name of one owner. Returns the name of the owner. Maybe null if no owner was set withICase.setOwner(ISecurityMember). Does not return null if theISecurityMemberwas deleted.useICase.tasks().all()Returns all child tasks.useICase.owners(). A case can have multiple owners. To not break existing applications, this will first remove all owners attached to this case and adds the new owner. By passing null it only will remove all owners. Sets the owner of the case.all and everything should be scoped to a worfklow context which is bound to a security context. always preferIWorkflowContext.scope everything to a a workflow context an useIWorkflowContext.getCaseQueryExecutor()scope everything to a a workflow context an useIWorkflowContext.getTaskQueryExecutor()useNoteuseNote.createdAt()useNote.id()useNote.content()useNote.author()useICase.notes()orITask.notes()multiple roles are allowed to start a process, useIProcessStart.roles()useIStartEventElement.getConfiguration()insteadnot longer persistent (if engine is restarted, the event bean is started again)not longer persistent (if engine is restarted, the event bean is started again)useITask.responsibles()followed byResponsibles.all()useITask.responsibles(), followed byResponsibles.all(),Responsible.get()andISecurityMember.getMemberName()useITask.expiry()followed byExpiry.responsibles(),ExpiryResponsibles.all()andExpiryResponsible.get()useITask.expiry()followed byExpiry.responsibles(),ExpiryResponsibles.all(),ExpiryResponsible.get()andISecurityMember.getMemberName()No longer use this method and there is no replacement available. There should be no use case to get the original activator.No longer use this method and there is no replacement available. There should be no use case to get the original activator.No longer use this method and there is no replacement available. There should be no use case to get the original activator.useITask.responsibles(), followed byResponsibles.add(ISecurityMember)useITask.expiry()followed byExpiry.responsibles()andExpiryResponsibles.add(ch.ivyteam.ivy.security.ISecurityMember)No longer use this method and there is no replacement available. There should be no use case to set the original activator.useIApplication.current()to get the current applicationscope everything to a workflow context and prevent using global workflow contet.aggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseisEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.since the introdution of multiple responsibles per task this makes no longer sense. to get the user who has created the case useCaseQuery.IFilterableColumns.creatorId().ch.ivyteam.ivy.workflow.query.CaseQuery.IFilterableColumns.userOrHisRolesAreInvolved(String, String) the activator is the same as the original responsible for the first task of case. to query cases itself we see no use case and we no longer support this method.grouping by identifier makes no sensegrouping by timestamps is inaccurate.grouping by timestamps is inaccurate.A case can have multiple activators. Therefore it makes no sense to order tasks by activator.This method does not have any effect, because a case can have multiple case owners.This method does not have any effect, because a case can have multiple case owners.This method does not have any effect, because a case can have multiple case owners.isGreaterOrEqualThan makes no sense on string fieldsisGreaterThan makes no sense on string fieldsisLowerOrEqualThan makes no sense on string fieldsisLowerThan makes no sense on string fieldsisEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.isGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.grouping by timestamps is inaccurate.grouping by identifier makes no sense.ch.ivyteam.ivy.workflow.query.SignalEventQuery.IStringColumnFilterQuery.isGreaterOrEqualThan(String) isGreaterOrEqualThan makes no sense on string fields.isGreaterThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerThan makes no sense on string fields.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.grouping by identifier makes no senseisGreaterOrEqualThan makes no sense on string fields.isGreaterThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerThan makes no sense on string fields.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating worker session id makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.aggregating task id makes no sense.aggregating worker session id makes no sense.aggregating string columns makes no sense.aggregating string columns makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.aggregating task id makes no sense.aggregating worker session id makes no sense.aggregating string columns makes no sense.aggregating string columns makes no sense.aggregating worker session id makes no sense.aggregating this field makes no sense.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.there should be no need to query for original responsiblethere should be no need to query for original responsiblethere should be no need to query for original responsiblech.ivyteam.ivy.workflow.query.TaskQuery.IFilterableColumns.userOrHisRolesAreInvolved(String, String) grouping by timestamp is inaccurategrouping by timestamp is inaccurategrouping by timestamp is inaccurategrouping by timestamps is inaccuratethere should be no need to query for original activatorthere should be no need to query for original activatorthere should be no need to query for original activatorgrouping by timestamp is inaccurategrouping by identifier makes no senseA task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.isGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.ch.ivyteam.ivy.workflow.query.WorkflowEventQuery.IStringColumnFilterQuery.isLowerOrEqualThan(String) isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.This API is no longer available, please useIBpmSignalReceivers.all(),IBpmSignalReceivers.matches(SignalCode)orIBpmSignalReceivers.contains(String)instead.use create().data("{\"id\" : \"XIVY-295\"}").makeCurrentTaskPersistent().send("issue:created") instead.a start can have multiple roles, therefore useIWebStartable.roles()not used anymore. no tasks are in this state.Database Value:
9not used anymore. tasks which become zombies will be deleted.Since the introduction of multiple task responsibles the following events will be writtenWorkflowEventKind.EVENT_TASK_ORIGINAL_RESPONSIBLE_ADDEDandWorkflowEventKind.EVENT_TASK_ORIGINAL_RESPONSIBLE_DELETEDSince the introduction of multiple responsibles the following events will be written:WorkflowEventKind.EVENT_TASK_RESPONSIBLE_ADDEDandWorkflowEventKind.EVENT_TASK_RESPONSIBLE_DELETEDuseIvyAsyncExecutor
-
Deprecated InterfacesInterfaceDescriptionuse
SubProcessCallStartandSubProcessCallinsteadUsech.ivyteam.ivy.bpm.exec.IBpmnProcessElementinstead.all and everything should be scoped to a worfklow context which is bound to a security context. always preferIWorkflowContext.useNoteuseICase.notes()orITask.notes()
-
Deprecated ClassesClassDescriptionuse
LazyDataModel. Primefaces has changed this interface in version 10 and 11.useIvyFreyaThemeinstead useSubProcessCalldirectly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)useIvyAsyncExecutor
-
Deprecated Enum Classes
-
Deprecated FieldsFieldDescription
-
Deprecated MethodsMethodDescriptionsession roles will be no longer supported in future. use
SessionChooser.anonymous().session roles will be no longer supported in future. useSessionChooser.anonymous().session roles will be no longer supported in future. useSubSessionChooser.anonymous().session roles will be no longer supported in future. useSubSessionChooser.anonymous().useBusinessDataRepository.current()insteaduseICaseMapService.current()insteaduse insteadVariables.names()useIHtmlDialogContext.appHomeLink()insteaduseIHtmlDialogContext.appHomeLink()insteaduseIHtmlDialogContext.coLink(String)insteaduseIHtmlDialogContext.fileLink(File)insteaduseIHtmlDialogContext.fileLink(String, boolean)insteadnot supported anymore. always returns empty string.useIHtmlDialogContext.loginLink()insteaduseIHtmlDialogContext.processStartListLink()insteadWebPage features was removed with 11.2. Use HtmlDialog instead.useIHtmlDialogContext.startRef(String)which behaves exactly the same wayuseIHtmlDialogContext.startLink(String)insteaduseIHtmlDialogContext.taskListLink()insteadthis feature is moved to the engine cockpit.instead useSubProcessCalland @{linkSubProcessCallStart.call(Object...)instead useSubProcessCalland @{linkSubProcessCallStart.call(Object...)instead useSubProcessCall,SubProcessCallStartParam.withParam(String, Object), and @{linkSubProcessCallStart.call(Object...)instead useSubProcessCallStart.find(SubProcessSearchFilter)useSubProcessSearchFilter.Builder.setSearchScope(SearchScope)with parameterSubProcessSearchFilter.SearchScope.APPLICATIONorSubProcessSearchFilter.SearchScope.PROJECT_AND_ALL_REQUIREDuseSubProcessSearchFilter.Builder.setSearchScope(SearchScope)with parameterSubProcessSearchFilter.SearchScope.PROJECT_AND_ALL_REQUIREDorSubProcessSearchFilter.SearchScope.PROJECTNewly-written code should use the date/time types defined injava.time.Newly-written code should use the date/time types defined injava.time.useAbstractProcessStartEventBean.getConfig()instead.instead useIProcessStartEventBeanRuntime.processStarter()directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)ch.ivyteam.ivy.process.extension.ICommonProcessExtensionConfigurationEditor.setConfiguration(String) directly bind your widgets to a config value viaExtensionUiBuilder.scriptField(String)orExtensionUiBuilder.textField(String)useAbstractProcessExtension.getConfig()insteaduseAbstractProcessExtension.getConfig()instead.IProcessExtension.setConfiguration(ProgramConfig)is used instead.useExtensionUiBuilder.scriptField(String)instead.useExtensionUiBuilder.scriptField(String)instead.no use-case with web-based inscriptionno use-case with web-based inscriptionuseAbstractProcessIntermediateEventBean.getConfig()insteaduseISecurityMember.getSecurityMemberId()session roles are no longer supported. useISecurityMember.isMember(IUserToken)session role is no longer supported. assign roles to user.grouping by identifier makes no senseisGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.UseIDocument.uuid()Attention: YOU SHOULD NOT USE THIS. If you use an external document provider like S3, documents are not available on the local file system, therefore the files needs and will be automatically cached on the local system. Always prefer using the following methods in the given order: -IDocumentContentReader.asStream()-IDocumentContentReader.asReader()-IDocumentContentReader.asBinary()-IDocumentContentReader.asString()If you like to pass a document for example as Mail attachment, then simply use the document directly, becauseIDocumentextendsDataStreamProvider.Attention: YOU SHOULD NOT USE THIS. If you use an external document provider like S3, documents are not available on the local file system, therefore the files needs and will be automatically cached on the local system. Always prefer using the following methods in the given order: -IDocumentContentReader.asStream()-IDocumentContentReader.asReader()-IDocumentContentReader.asBinary()-IDocumentContentReader.asString()If you like to pass a document for example as Mail attachment, then simply use the document directly, becauseIDocumentextendsDataStreamProvider.Use get(StrinuseICase.tasks().allActive()Returns all active child tasks.useICase.owners(). A case can have multiple owners. This will return only one owner. Returns the owner of the case. Maybe null if no owner was set withICase.setOwner(ISecurityMember).
The intend of the owner is only for descriptive purpose and has no influence on the behavior of the Workflow Engine. This may can be used for example in Workflow UIs to search and filter in case lists.useICase.owners(). A case can have multiple owners. This will return only the name of one owner. Returns the name of the owner. Maybe null if no owner was set withICase.setOwner(ISecurityMember). Does not return null if theISecurityMemberwas deleted.useICase.tasks().all()Returns all child tasks.useICase.owners(). A case can have multiple owners. To not break existing applications, this will first remove all owners attached to this case and adds the new owner. By passing null it only will remove all owners. Sets the owner of the case.scope everything to a a workflow context an useIWorkflowContext.getCaseQueryExecutor()scope everything to a a workflow context an useIWorkflowContext.getTaskQueryExecutor()useNote.createdAt()useNote.id()useNote.content()useNote.author()multiple roles are allowed to start a process, useIProcessStart.roles()useIStartEventElement.getConfiguration()insteadnot longer persistent (if engine is restarted, the event bean is started again)not longer persistent (if engine is restarted, the event bean is started again)useITask.responsibles()followed byResponsibles.all()useITask.responsibles(), followed byResponsibles.all(),Responsible.get()andISecurityMember.getMemberName()useITask.expiry()followed byExpiry.responsibles(),ExpiryResponsibles.all()andExpiryResponsible.get()useITask.expiry()followed byExpiry.responsibles(),ExpiryResponsibles.all(),ExpiryResponsible.get()andISecurityMember.getMemberName()No longer use this method and there is no replacement available. There should be no use case to get the original activator.No longer use this method and there is no replacement available. There should be no use case to get the original activator.No longer use this method and there is no replacement available. There should be no use case to get the original activator.useITask.responsibles(), followed byResponsibles.add(ISecurityMember)useITask.expiry()followed byExpiry.responsibles()andExpiryResponsibles.add(ch.ivyteam.ivy.security.ISecurityMember)No longer use this method and there is no replacement available. There should be no use case to set the original activator.useIApplication.current()to get the current applicationscope everything to a workflow context and prevent using global workflow contet.aggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseaggregating this field makes no senseisEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.since the introdution of multiple responsibles per task this makes no longer sense. to get the user who has created the case useCaseQuery.IFilterableColumns.creatorId().ch.ivyteam.ivy.workflow.query.CaseQuery.IFilterableColumns.userOrHisRolesAreInvolved(String, String) the activator is the same as the original responsible for the first task of case. to query cases itself we see no use case and we no longer support this method.grouping by identifier makes no sensegrouping by timestamps is inaccurate.grouping by timestamps is inaccurate.A case can have multiple activators. Therefore it makes no sense to order tasks by activator.ordering by CLOB fields is not possible.This method does not have any effect, because a case can have multiple case owners.This method does not have any effect, because a case can have multiple case owners.This method does not have any effect, because a case can have multiple case owners.isGreaterOrEqualThan makes no sense on string fieldsisGreaterThan makes no sense on string fieldsisLowerOrEqualThan makes no sense on string fieldsisLowerThan makes no sense on string fieldsisEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.isGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.grouping by timestamps is inaccurate.grouping by identifier makes no sense.ch.ivyteam.ivy.workflow.query.SignalEventQuery.IStringColumnFilterQuery.isGreaterOrEqualThan(String) isGreaterOrEqualThan makes no sense on string fields.isGreaterThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerThan makes no sense on string fields.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.grouping by identifier makes no senseisGreaterOrEqualThan makes no sense on string fields.isGreaterThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerThan makes no sense on string fields.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating this field makes no sense.aggregating worker session id makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.aggregating start element pid makes no sense.Max aggregation on a string field makes no sense.Max aggregation on a string field makes no sense.aggregating task id makes no sense.aggregating worker session id makes no sense.aggregating string columns makes no sense.aggregating string columns makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.aggregating start element pid makes no sense.Min aggregation on a string field makes no sense.Min aggregation on a string field makes no sense.aggregating task id makes no sense.aggregating worker session id makes no sense.aggregating string columns makes no sense.aggregating string columns makes no sense.aggregating worker session id makes no sense.aggregating this field makes no sense.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.there should be no need to query for original responsiblethere should be no need to query for original responsiblethere should be no need to query for original responsiblech.ivyteam.ivy.workflow.query.TaskQuery.IFilterableColumns.userOrHisRolesAreInvolved(String, String) grouping by timestamp is inaccurategrouping by timestamp is inaccurategrouping by timestamp is inaccurategrouping by timestamps is inaccuratethere should be no need to query for original activatorthere should be no need to query for original activatorthere should be no need to query for original activatorgrouping by timestamp is inaccurategrouping by identifier makes no senseA task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.ordering by CLOB fields is not possible.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.A task can have multiple activators. Therefore it makes no sense to order tasks by activator.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isLowerOrEqualThan makes no sense on string fields.isEqual for date is error prone because it may compares milliseconds.isNotEqual for date is error prone because it may compares milliseconds.isGreaterOrEqualThan on string fields make no sense.isGreaterThan on string fields make no sense.ch.ivyteam.ivy.workflow.query.WorkflowEventQuery.IStringColumnFilterQuery.isLowerOrEqualThan(String) isLowerOrEqualThan on string fields make no sense.isLowerThan on string fields make no sense.This API is no longer available, please useIBpmSignalReceivers.all(),IBpmSignalReceivers.matches(SignalCode)orIBpmSignalReceivers.contains(String)instead.use create().data("{\"id\" : \"XIVY-295\"}").makeCurrentTaskPersistent().send("issue:created") instead.a start can have multiple roles, therefore useIWebStartable.roles()
-
Deprecated ConstructorsConstructorDescription
-
Deprecated Enum ConstantsEnum ConstantDescriptionnot used anymore. cases which become zombies will be deleted.not used anymore. no tasks are in this state.
Database Value:
9not used anymore. tasks which become zombies will be deleted.Since the introduction of multiple task responsibles the following events will be writtenWorkflowEventKind.EVENT_TASK_ORIGINAL_RESPONSIBLE_ADDEDandWorkflowEventKind.EVENT_TASK_ORIGINAL_RESPONSIBLE_DELETEDSince the introduction of multiple responsibles the following events will be written:WorkflowEventKind.EVENT_TASK_RESPONSIBLE_ADDEDandWorkflowEventKind.EVENT_TASK_RESPONSIBLE_DELETED