Namespace Casewhere.Models
Namespaces
Casewhere.Models.ActivityDefinitions
Casewhere.Models.DevOpsPackages
Casewhere.Models.EditingDocuments
Casewhere.Models.EventTriggers
Casewhere.Models.IdPConnections
Casewhere.Models.RuntimeSchedulers
Casewhere.Models.SystemSchemas
Casewhere.Models.TextResources
Casewhere.Models.WorkerSiteComponents
Casewhere.Models.WorkflowBuilds
Casewhere.Models.WorkflowMonitors
Casewhere.Models.WorkflowTests
Classes
Represents an abstract activity definition. It is used in Workflow Definition and can be these types: FormActivityDefinition, LoopActivityDefinition, ScriptedActivityDefinition, WorkflowActivityDefinition.
ActivityDefinitionConcurrencySetting
Represents an attribute that holds an array of values.
Represents a boolean attribute.
Represents a component data source that use in Form Activity Definition
Represents a DataClass reference to Workflow definition
Represents a base class for data attributes.
Represents a base class for data classes. Casewhere is not designed for any specific business domain, so it does not provide a fixed, built-in data model. Instead, you, as a Casewhere designer, will need to instruct Casewhere how you would like to store data by defining data classes and the relationships among them.
Represents a data class attribute.
Represents a data source entity. Where applications and components fetch data via data sources instead of opening connections directly to the database. It base on a Primary Data Class offers the output data structure (same as a View in database) A data source can serve different purposes. You can access data sources from widgets, workflows, or even from worker sites.
DataSourceAuditLogAttributeModel
Represents a data class associated with a data source.
Represents a data trigger. It defines a way Casewhere to execute a workflow when data changes.
Represents a DateTime attribute.
Represents a file that import and used in the Casewhere System entity.
Represents a file/document attribute.
DynamicWorkflowActivityDefinition
Represents an abstract base class for entities in Casewhere.
Represents an attribute that holds an enumeration value.
Represents a field definition.
Represents an attribute that indicates a foreign key relationship between two data classes.
Represents a form activity definition. It contains information to build a UI activity in Casewhere workflow and collect information from or display information to end-users
Represents a custom attribute for a GUID data type.
Represents an attribute that holds an integer value.
Represents an internal data class.
Represents a language entity.
Represents the localization settings that use in Worker site
Represents a long attribute.
Represents a loop activity definition. It contains information to loop through the data objects filtered by a given condition and trigger a new workflow per data object
repeat every Recurrence months on Day
Represents an attribute that holds an object value.
Represents a plugin entity. Casewhere provides a flexible plugin framework to make it easy to extend your Casewhere solution with more functionalities. From simple tasks like sending emails to complex ones such as executing a SQL query, almost everything can be done using a Casewhere plugin. Casewhere plugins can be developed independently, installed on-demand, and invoked at runtime.
Represents a plugin data class.
Represents the metadata of a plugin.
Represents a plugin policy. Plugin security is vital. Casewhere executes plugins in a partially trusted AppDomain - separate from Casewhere's core - to mitigate the risk of plugins being exploited to execute malicious code. The 'Is Public' setting is optional because some plugins are too sensitive to be exposed to a web interface.
Casewhere is a system for handling business processes. A process in Casewhere is the “definition” of what data a case can contain. A process could for example be “Recruitment”. It will contain all the specifications and definitions of what carrying out recruitment means. This process will “contain” multiple instances of recruitment efforts, e.g. the processing of the recruitment of John Doe would be one instance. The recruitment of Jane Doe would be another instance. Instances of a process we call “cases”
Represents a product entity. Casewhere is a case management, process standardization, and workflow automation system. Casewhere makes it possible to create seamlessly integrated processes that tie together applications, internal and external actors, and data stores. With its extremely open architecture, the user can easily and quickly build up a solution for their organization where all the business systems work and share data. To do this, Casewhere provides a variety of building blocks (products) that you can combine into a solution that serves your needs.
Represents an abstract class for recurrence type of Scheduler
Represents a scheduler entity.
Represents a scripted activity definition. It contains information to execute a C# script
Represents a string attribute.
Represents a system log rule. The Rule is used to masking the sensitive values in the Log message.
Represents a text resource.
Represents a web trigger entity. With web triggers, you can expose a Web API endpoint for your external systems to trigger a workflow in Casewhere. Using web triggers is one of the most popular ways to integrate other systems with Casewhere.
repeat every Recurrence weeks on DayOfWeeks(Mon, Tue...) at hh:mm
Represents a workflow activity definition. It contains information to execute another workflow
WorkflowActivityDefinitionBase
Represents a version 2 workflow activity definition. It contains information to execute another workflow
Represents a workflow definition. It defines how workflows work, In Casewhere, all actions that happen around cases require a workflow to execute, whether they're buying parking tickets, applying for jobs, or simply sending newsletters. Casewhere provides two types of workflows: UI workflows: Display data to your users or collect information from them with UI elements.UI workflows are triggered from widgets by end-users.Casewhere provides a workflow definition editor with a form builder to enable you to design complex, rich UI activities. Automatic workflows: Are triggered automatically by an event in the system, a change in the database, or other workflows.Casewhere provides a wide range of workflow triggers, so you have all the necessary flexibilities to design solutions for different sophisticated scenarios.
Represents a workflow step definition.
WorkflowValidationRuleMetadata
Represents the metadata for a workflow validation rule.
repeat every Recurrence years on Day/Month
Interfaces
Enums
Represents the context of a component data source.
Priority order of workflows that can run in background at the same time: Urgent > As Soon As Possible > Normal > Low.