Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluate rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluate rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. Some embodiments store only unique fragments, resulting in a significant reduction in storage requirements and an extremely efficient way of processing huge amounts of data (e.g., millions of documents) for document production. The messages and fragments are in internal formats under control of the document architecture system.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. Some embodiments store only unique fragments, resulting in a significant reduction in storage requirements and an extremely efficient way of processing huge amounts of data (e.g., millions of documents) for document production. The messages and fragments are in internal formats under control of the document architecture system.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluable rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: A local delivery service (LDS) operates in an enterprise computer network as a proxy for a communications server (CS) computer operating in a cloud computing environment. The LDS pulls a queue repository maintained by the CS and retrieves an output item flagged by the CS for local delivery. The output item has a document and associated configuration information specifying an application domain in the cloud computing environment and delivery settings specific to the application domain maintained by the CS. The LDS translates the delivery settings and routes the document to the connectors of communications channels of the enterprise computer network. In this way, documents produced by the CS in the cloud can be delivered locally to disparate destinations on the enterprise computer network without having to open individual ports in a firewall of the enterprise computer network to connect the CS with communications channels of the enterprise computer network.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluable rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. The messages and fragments are in internal formats under control of the document architecture system. The renditions are in final formats that can be delivered, for instance, via an output connector to various output delivery channels.

Abstract: A local delivery service (LDS) operates in an enterprise computer network as a proxy for a communications server (CS) computer operating in a cloud computing environment. The LDS pulls a queue repository maintained by the CS and retrieves an output item flagged by the CS for local delivery. The output item has a document and associated configuration information specifying an application domain in the cloud computing environment and delivery settings specific to the application domain maintained by the CS. The LDS translates the delivery settings and routes the document to the connectors of communications channels of the enterprise computer network. In this way, documents produced by the CS in the cloud can be delivered locally to disparate destinations on the enterprise computer network without having to open individual ports in a firewall of the enterprise computer network to connect the CS with communications channels of the enterprise computer network.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. The messages and fragments are in internal formats under control of the document architecture system. The renditions are in final formats that can be delivered, for instance, via an output connector to various output delivery channels.

Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.

Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. Some embodiments store only unique fragments, resulting in a significant reduction in storage requirements and an extremely efficient way of processing huge amounts of data (e.g., millions of documents) for document production. The messages and fragments are in internal formats under control of the document architecture system.

Abstract: A document architecture system includes an intelligent document processing engine that can receive raw data streamed from external data source(s), analyze the raw data to identify triggering events, apply rules to the triggering events identified, break down the raw data accordingly, and generating messages in an internal format to represent the pieces of data without any formatting or layout information. The messages can be augmented with custom metadata and stored as fragments that reference, but that do not physically incorporate, the messages. The stored fragments can be used by the document process engine to intelligently render documents and versions thereof. Some embodiments store only unique fragments, resulting in a significant reduction in storage requirements and an extremely efficient way of processing huge amounts of data (e.g., millions of documents) for document production. The messages and fragments are in internal formats under control of the document architecture system.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluable rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: A document production system may construct a document from fragments based on a theme associated with the document. The theme may contain section(s), each section having an access control list (ACL) associated therewith. The ACL may specify role-based user group(s) and permission(s) for the role-based user group(s). The system may evaluable rules applicable to the document. At least one rule may pertain to the ACL(s). The evaluation may include, at least in part, utilizing user login information received over a network from a client device. In constructing the document, the system may assemble the document in accordance with the rules and utilizing the fragments and meta information that describes the document. The system may render the document thus assembled utilizing the ACL, generate a view of the document, and communicate the view of the document over the network to the client device for presentation on the client device.

Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.

Abstract: Disclosed communication flow modeling solution is significantly streamlined in a user friendly way to shield users from the technical complexities usually required. At design time, an orchestration flow modeling application receives user instruction to open or create a communication flow modeling project. Per configuration specific to an enterprise associated with the user, a custom drag-and-drop communication flow modeling environment with a canvas and modeling entities is provided. Responsive to the user dragging and dropping a set of modeling entities from the menu onto the communication flow modeling canvas and drawing connections between them, the orchestration flow modeling application logically connects the modeling entities to form a valid communication flow and stores it in a database. The communication flow undergoes an approval process. Once approved, it is activated for execution by an orchestration server.