Attachment Element/en - Versionsgeschichte

Cg: /* Attachment in an Activity Diagram */

2022-07-04T08:32:14Z

Attachment in an Activity Diagram

← Nächstältere Version		Version vom 4. Juli 2022, 08:32 Uhr
Zeile 8:		Zeile 8:

	=== Attachment in an Activity Diagram ===		=== Attachment in an Activity Diagram ===
	When an attachment is '''dragged''' into a compound action's network, an attachment-reading step action is generated. ~~This~~ ''attachment step'' provides the file at its output pin, ~~when~~ ~~triggered~~ or ~~autostarted~~ (just like any other step in the diagram).		When an attachment is '''dragged''' into a compound action's network, an attachment-reading step action is generated. When triggered or autostarted, this ''attachment step'' provides the file's name or contents at its output pin. Thus, the attachment step behaves just like any other step in the diagram.

	The step is configurable to either provide the filename or its contents at its output pin. The default is to generate the filename. Thus, to get the full path of an attachment, make sure that the output representation is set to "pathName" and connect the attachment step's output to whichever step needs the path.		The step is configurable to either provide the filename or its contents at its output pin. The default is to generate the filename. Thus, to get the full path of an attachment, make sure that the output representation is set to "''pathName''" and connect the attachment step's output to whichever step needs the path.

	[[Datei:point_right.png\|20px]] Notice that all of the attachments' filenames must be distinct. For that, the name of the file is not required to be the same as the item's name in the navigation tree. When copy-pasting or dragging attachments into the tree, expecco may silently change the filename (but not the name), if another attachment already exists by that filename. In that case, the underlying filename may be different from its name shown in the tree. Thus, you should never use the tree item's name, but always refer to its filename (via the output pin).		[[Datei:point_right.png\|20px]] Notice that all of the attachments' filenames must be distinct. For that, the name of the file is not required to be the same as the item's name in the navigation tree. When copy-pasting or dragging attachments into the tree, expecco may silently change the filename (but not the name), if another attachment already exists by that filename. In that case, the underlying filename may be different from its name shown in the tree. Thus, you should never use the tree item's name, but always refer to its filename (via the output pin).

Cg: /* Encrypting an Attachment's Contents */

2021-05-05T20:54:12Z

Encrypting an Attachment's Contents

← Nächstältere Version		Version vom 5. Mai 2021, 20:54 Uhr
Zeile 93:		Zeile 93:
	== Encrypting an Attachment's Contents ==		== Encrypting an Attachment's Contents ==
	New with version 21.1:<br>It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.		New with version 21.1:<br>It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.
	Expecco will use ~~ONE~~ single password to encrypt all documents within a suite, and will ask when the first such		Expecco will use '''one''' single password to encrypt all documents within a suite, and will ask when the first such
	access happens. The password will be remembered for the duration of the session.		access happens. The password will be remembered for the duration of the session.

Cg: /* Encrypting an Attachment's Contents */

2021-05-05T18:37:05Z

Encrypting an Attachment's Contents

← Nächstältere Version		Version vom 5. Mai 2021, 18:37 Uhr
Zeile 92:		Zeile 92:

	== Encrypting an Attachment's Contents ==		== Encrypting an Attachment's Contents ==
	New with ~~Von~~ 21.1:<br>It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.		New with version 21.1:<br>It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.
	Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such		Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such
	access happens. The password will be remembered for the duration of the session.		access happens. The password will be remembered for the duration of the session.

Cg: /* Encrypting an Attachment's Contents (vsn21.1) */

2021-05-05T18:36:47Z

Encrypting an Attachment's Contents (vsn21.1)

← Nächstältere Version		Version vom 5. Mai 2021, 18:36 Uhr
Zeile 91:		Zeile 91:
	For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].		For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].

	== Encrypting an Attachment's Contents ~~(vsn21.1)~~ ==		== Encrypting an Attachment's Contents ==
	It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.		New with Von 21.1:<br>It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.
	Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such		Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such
	access happens. The password will be remembered for the duration of the session.		access happens. The password will be remembered for the duration of the session.

Cg: /* Encrypting an Attachment's Contents */

2021-05-05T18:34:48Z

Encrypting an Attachment's Contents

← Nächstältere Version		Version vom 5. Mai 2021, 18:34 Uhr
Zeile 91:		Zeile 91:
	For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].		For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].

	== Encrypting an Attachment's Contents ==		== Encrypting an Attachment's Contents (vsn21.1) ==
	It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.		It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.
	Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such		Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such
	access happens. The password will be remembered for the duration of the session.		access happens. The password will be remembered for the duration of the session.

			The encrypt function is found in the context menu of the attachment's tree item.

	== Special Attachments (Wellknown Attachment Types) ==		== Special Attachments (Wellknown Attachment Types) ==

Cg: /* Editing an Attachment's Contents */

2021-05-05T18:33:52Z

Editing an Attachment's Contents

← Nächstältere Version		Version vom 5. Mai 2021, 18:33 Uhr
Zeile 89:		Zeile 89:

	Attachments can be edited using the attachment editor, which is shown when an attachment tree item is selected.		Attachments can be edited using the attachment editor, which is shown when an attachment tree item is selected.
	For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].		For most simple textual formats, the builtin text editor is sufficient. However, if you prefer your own editor, or a special editing application is to be used, you can configure the editor as-per-mime type in the "external tools" configuration dialog. Details are found in the [[Attachment_Editor \| attachment editor's documentation]].

			== Encrypting an Attachment's Contents ==
			It may be useful to keep login/password data in an attachment, although you don't want to get them exposed, in case the suite gets copied to unauthorized users. For this, you can encrypt an attachment's contents, to be only readable, if the user provides a correct password whenever the document's contents is fetched later.
			Expecco will use ONE single password to encrypt all documents within a suite, and will ask when the first such
			access happens. The password will be remembered for the duration of the session.

	== Special Attachments (Wellknown Attachment Types) ==		== Special Attachments (Wellknown Attachment Types) ==

Cg: /* Data Representation */

2020-11-13T15:43:56Z

Data Representation

← Nächstältere Version		Version vom 13. November 2020, 15:43 Uhr
Zeile 49:		Zeile 49:
	: generates a URL of the form "file://<path>"		: generates a URL of the form "file://<path>"

	;String		;String (''Contents as String'')
	: the file is read into one (possibly big) single-byte string. No decoding is performed. This representation may not be appropriate for UTF-8 encoded files, if your intent is to process the contents. However, it is most useful, if the contents is to be passed on to other processing steps, passed to external programs, or to be send out via a socket. If the contents is shown in expecco, or processed by any of expecco's functions, it is interpreted as ISO8859 encoded.		: the file is read into one (possibly big) single-byte string. No decoding is performed. This representation may not be appropriate for UTF-8 encoded files, if your intent is to process the contents. However, it is most useful, if the contents is to be passed on to other processing steps, passed to external programs, or to be send out via a socket. If the contents is shown in expecco, or processed by any of expecco's functions, it is interpreted as ISO8859 encoded.

	;UTF8 String		;UTF8 String (''Contents as UTF-8 String'')
	: the data is read as a single string, and interpreted as an UTF-8 encoded string. The output may be a single-byte or a multi-byte string, depending on the presence of characters with a codepoint > 255.		: the data is read as a single string, and interpreted as an UTF-8 encoded string. The output may be a single-byte or a multi-byte string, depending on the presence of characters with a codepoint > 255.

	;StringCollection		;StringCollection (''Contents as Collection of Lines'')
	: the file is read into a collection of single-byte string lines. No decoding is performed.		: the file is read into a collection of single-byte string lines. No decoding is performed.

	;Linewise		;Linewise (''Contents as Individual Lines'')
	: the file is read line-wise, and each line is send to the output pin as a separate datum. This will trigger follow-up actions once for every line in the original document.		: the file is read line-wise, and each line is send to the output pin as a separate datum. This will trigger follow-up actions once for every line in the original document.

Zeile 66:		Zeile 66:
	;Bitmap Image		;Bitmap Image
	: the file is assumed to contain a bitmap image in one of the supported formats (PNG, JPEG, GIF, TIFF and many others).		: the file is assumed to contain a bitmap image in one of the supported formats (PNG, JPEG, GIF, TIFF and many others).

			;JSON Object
			: a single JSON object is read from the file and presented at the output

			;Multiple JSON Objects
			: multiple JSON objects are read from the file and presented at the output

	The following representations are only possible with URL attachments. They automatically decode the fetched document into the expecco internal Unicode format, from a number of common document encodings (for example, ISO 8859-x, UTF-8, ASCII, and many other).		The following representations are only possible with URL attachments. They automatically decode the fetched document into the expecco internal Unicode format, from a number of common document encodings (for example, ISO 8859-x, UTF-8, ASCII, and many other).

Cg: /* Data Representation */

2020-11-13T15:39:31Z

Data Representation

← Nächstältere Version		Version vom 13. November 2020, 15:39 Uhr
Zeile 53:		Zeile 53:

	;UTF8 String		;UTF8 String
	: the data is read as a single string, and interpreted as an UTF-8 encoded string. The output my be a single-byte or a multi-byte string, depending on the presence of characters with a codepoint > 255.		: the data is read as a single string, and interpreted as an UTF-8 encoded string. The output may be a single-byte or a multi-byte string, depending on the presence of characters with a codepoint > 255.

	;StringCollection		;StringCollection

Cg: /* Data Representation */

2020-11-13T15:38:53Z

Data Representation

← Nächstältere Version		Version vom 13. November 2020, 15:38 Uhr
Zeile 50:		Zeile 50:

	;String		;String
	: the file is read into one (possibly big) single-byte string. No decoding is performed. This representation may not be appropriate for UTF-8 encoded files, if your intent is to process the contents. However, it is most useful, if the contents is to be passed on to other processing steps, passed to external programs, or to be send out via a socket.		: the file is read into one (possibly big) single-byte string. No decoding is performed. This representation may not be appropriate for UTF-8 encoded files, if your intent is to process the contents. However, it is most useful, if the contents is to be passed on to other processing steps, passed to external programs, or to be send out via a socket. If the contents is shown in expecco, or processed by any of expecco's functions, it is interpreted as ISO8859 encoded.

	;UTF8 String		;UTF8 String

Cg: /* Attachment in an Activity Diagram */

2020-11-13T15:35:32Z

Attachment in an Activity Diagram

← Nächstältere Version		Version vom 13. November 2020, 15:35 Uhr
Zeile 8:		Zeile 8:

	=== Attachment in an Activity Diagram ===		=== Attachment in an Activity Diagram ===
	When an attachment is dragged into a compound action's network, an attachment-reading step action is generated. This ''attachment step'' provides the file at its output pin, when triggered or autostarted (just like any other step in the diagram).		When an attachment is '''dragged''' into a compound action's network, an attachment-reading step action is generated. This ''attachment step'' provides the file at its output pin, when triggered or autostarted (just like any other step in the diagram).

	The step is configurable to either provide the filename or its contents at its output pin. The default is to generate the filename. Thus, to get the full path of an attachment, make sure that the output representation is set to "pathName" and connect the attachment step's output to whichever step needs the path.		The step is configurable to either provide the filename or its contents at its output pin. The default is to generate the filename. Thus, to get the full path of an attachment, make sure that the output representation is set to "pathName" and connect the attachment step's output to whichever step needs the path.