EProcedure Back-office - Revision history

Ictu mavi.cristache at 09:55, 1 July 2021

2021-07-01T09:55:51Z

2021-07-01T09:53:42Z

2021-07-01T09:30:09Z

typo

2021-06-07T11:37:50Z

2021-06-04T11:02:33Z

2021-06-04T11:02:26Z

2021-06-04T10:59:03Z

2021-06-04T10:52:40Z

2021-06-04T09:50:00Z

2021-06-03T14:48:06Z

← Older revision		Revision as of 09:55, 1 July 2021
Line 1:		Line 1:
−	The eProcedure Back-office application collaboration consists of two high-level ~~component~~ realizing the functionality needed. It encompasses:	+	The eProcedure Back-office application collaboration consists of two high-level components realizing the functionality needed. It encompasses:

	* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;		* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;

← Older revision		Revision as of 09:53, 1 July 2021
Line 2:		Line 2:

	* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;		* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;
−	* (front-end) a UI for user tasks to ~~analyze~~ wrong subscriptions.	+	* (front-end) a UI for user tasks to analyse wrong subscriptions.

@@ Line 20: / Line 20: @@
 |-
 |[[eProcedure Back-office Front-end]]
-|This component provides a UI for user tasks to analyze wrong subscriptions.
+|This component provides a UI for user tasks to analyse wrong subscriptions.
 |[[Subscription and Notification Pattern|S&N]]
 |}

@@ Line 16: / Line 16: @@
 |-
 |[[eProcedure Back-office Backend]]
-|This component implements backend functionlaity like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
+|This component implements backend functionality like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
 |[[Subscription and Notification Pattern|S&N]]
 |-

@@ Line 1: / Line 1: @@
 The eProcedure Back-office application collaboration consists of two high-level component realizing the functionality needed. It encompasses:
-* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
+* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;
 * (front-end) a UI for user tasks to analyze wrong subscriptions.

← Older revision		Revision as of 11:02, 4 June 2021
Line 1:		Line 1:
−	The eProcedure Back-office application collaboration consists of two high-level component realizing the functionality needed.	+	The eProcedure Back-office application collaboration consists of two high-level component realizing the functionality needed. It encompasses:
		+
		+	* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
		+	* (front-end) a UI for user tasks to analyze wrong subscriptions.

← Older revision		Revision as of 09:50, 4 June 2021
Line 1:		Line 1:
−	The eProcedure Back-office collaboration consists of ~~one~~ high-level component realizing the functionality needed..	+	The eProcedure Back-office application collaboration consists of two high-level component realizing the functionality needed.
		+
		+

	<gallery widths="400" perrow="1" caption="Graphic representations of the eProcedure Back-office application collaboration">		<gallery widths="400" perrow="1" caption="Graphic representations of the eProcedure Back-office application collaboration">