https://pranke.com/hilfe/ 2026-04-05T22:11:14+00:00 https://pranke.com/hilfe/ https://pranke.com/hilfe/lib/exe/fetch.php?media=favicon.ico text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:automatisierung&rev=1708413315&do=diff Naming convention for automation For the automations it is a good idea to simply take the name of the job to be triggered as the name, to avoid misunderstandings and to save reinventing a name. text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:jobs&rev=1708413315&do=diff Naming conventions for jobs Inbound Jobs Inbound stands for messages sent to your in-house system from the outside. Convention: <i> <No.> <Description> Here is an example of the inbound job naming convention: ---------- Outbound Jobs Outbound stands for messages sent from your in-house system to the outside world. text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:kommunikationskanaele&rev=1708413315&do=diff Naming convention for communication channels For the communication channels, it is convenient to form the short name of the channel type and the direction followed by an individual name. convention: <channel type>.<direction>.<individual name> text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:mappings&rev=1708413315&do=diff Naming conventions for mappings In order for a user or administrator to quickly recognize from which source object to which target object is mapped, we recommend naming your mappings as follows: convention <source type> .to. <Target type>. The name of the source and destination type can be found in the text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:repositories&rev=1708413315&do=diff Naming convention for repositories It is a good idea for a repository to have the same name as the namespace specified in the type library according to Naming conventions for interface types. * Recognition component = namespace * analysis component = namespace * write component = namespace text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:schnittstellen&rev=1708413315&do=diff Naming conventions for interface types Name type library For the naming of the DLL file usually the identifiers of the host system to be served or the interface in general are used. Ideally in such a way that the designation remains unambiguously identifiable and also speaking. The designation of the namespace should ideally be kept identical. text/html 2024-02-20T08:15:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://pranke.com/hilfe/doku.php?id=en:howtos:namenskonventionen:start&rev=1708413315&do=diff Naming conventions Introduction to the topic Naming conventions are recommendations for eBiss administrators and integrators for naming identifiers (names) for objects in the eBiss environment. By using them, the names of these objects are formed uniformly, supporting the