ART Scenario Editor - Revision history

Mligtvoet: moved form parameters to the end of the page

2020-07-08T12:58:58Z

moved form parameters to the end of the page

2020-07-08T12:53:10Z

2020-02-26T15:19:51Z

2020-02-26T15:18:06Z

2017-02-22T09:35:22Z

‎Introduction

2017-01-22T13:18:14Z

‎Introduction

2017-01-22T13:17:03Z

2017-01-22T13:16:33Z

‎Introduction

2017-01-22T13:16:07Z

2017-01-22T13:14:58Z

@@ Line 45: / Line 45: @@
 ===Editing the concepts of a transaction===
 [[File:ScenarioEditor-transaction4.jpg|750px]]
 =Form parameters=
@@ Line 92: / Line 114: @@
 | art v1.5.3
 |}

@@ Line 1: / Line 1: @@
 <!--{{Underconstruction}}-->
-== Introduction ==
+{{:ART_Scenario_Introduction}}
 == Creating a scenario ==

@@ Line 114: / Line 114: @@
 [[File:Page-leave-message.png|400px]]
-Navigating away from the page without saving the changes or cancelling the edit will leave the lock in place. If the same user attempts to edit the item at a later time the lock will be cleared automatically, if another user attempt to edit the item a message is displayed that the item is locked:
+Navigating away from the page without saving the changes or cancelling the edit will leave the lock in place. If the same user attempts to edit the item at a later time the lock will be cleared automatically, if another user attempts to edit the item a message is displayed that the item is locked:
 [[File:Scenario-lock-message.png|750px]]
-It is possible to break the lock at this time, be sure that there's no other user is actually working on this item before breaking a lock.
+It is possible to break the lock at this time, be sure that no other user is actually working on this item before breaking a lock.
 Project administrators can access an overview of all locks for the project on the Status tab of the Project Information page:

← Older revision		Revision as of 15:18, 26 February 2020
Line 107:		Line 107:
	\| art v1.5.3		\| art v1.5.3
	\|}		\|}
		+
		+	=Locking=
		+
		+	ART uses item level locking to prevent multiple users form editing the same item. When an item is edited this item and all children and parents of this item are locked. Locks are released when the changes are saved or the action is cancelled, when navigating away from the page a warning is displayed:
		+
		+	[[File:Page-leave-message.png\|400px]]
		+
		+	Navigating away from the page without saving the changes or cancelling the edit will leave the lock in place. If the same user attempts to edit the item at a later time the lock will be cleared automatically, if another user attempt to edit the item a message is displayed that the item is locked:
		+
		+	[[File:Scenario-lock-message.png\|750px]]
		+
		+	It is possible to break the lock at this time, be sure that there's no other user is actually working on this item before breaking a lock.
		+	Project administrators can access an overview of all locks for the project on the Status tab of the Project Information page:
		+
		+	[[File:Scenario-project-locks.png\|750px]]
		+
		+	Individual locks can be cleared here and all locks for a particular user can also be cleared here.
		+	The Status tab on the DECOR administration page shows the locks for all projects:
		+
		+	[[File:Scenario-decor-locks.png\|750px]]
		+
		+	Individual locks can be cleared here and all locks for a particular user can also be cleared here.

@@ Line 1: / Line 1: @@
 <!--{{Underconstruction}}-->
 == Introduction ==
-Scenarios are a container for transaction groups and transactions and will typically represent a health care use case, e.g. a Medication Prescription or a Radiology Examination.
+Scenarios are a container for transaction groups and transactions and will typically represent a health care use case, e.g. a Medication Prescription or a Radiology Examination. With that, scenarios/transaction provide the usage context as starting communicating without knowing why is not suitable.
 Transaction groups contain Transactions. There are two categories of transactions.

@@ Line 5: / Line 5: @@
 Transaction groups contain Transactions. There are two categories of transactions.
-Category 1: The pair of "initial" and "back" used in the messaging paradigm where an initial information transfer evokes a response message in terms of an acknowledgement or in a query/response environment.
+Category 1: The pair of "initial" and "back" used in the messaging paradigm where an initial information transfer evokes a response message in terms of an acknowledgement or in a query/response environment. This transaction typically has a sender and a receiver interacting.
 [[File:ScenarioEditor-transaction1.jpg|750px]]
-Category 2: The "stationary" transaction that is a self-referencing transaction for example to create a document.
+Category 2: The "stationary" transaction that is a self-referencing transaction for example to create a document. This interaction typically has a "sender" only, that is more a creator of the document. Sending and receiving aspects are not part of this category of transaction and handled separately.
 [[File:ScenarioEditor-transaction2.jpg|750px]]

@@ Line 11: / Line 11: @@
 [[File:ScenarioEditor-transaction2.jpg|750px]]
-Transactions represent a (sub)set of concepts from a dataset and add cardinality, conformance and possible conditions to them so they reflect the use case demands appropriately.
+Transactions represent a (sub)set of concepts from a dataset and add cardinality, conformance and possible conditions to them so they reflect the use case demands appropriately. A transaction typically has a reference to a representing template, that is the technical representation of the transaction and its underlying concepts.
 [[File:ScenarioEditor-transaction3.jpg|750px]]