Robotic Process Automation (RPA) in Desktop Publishing

Inhaltsverzeichnis

1. Frontmatter

2. Chapter 1. Desktop Publishing

   Ennis Gündoğan

   Abstract

   DTP, or “desktop publishing,” was born in 1985 through the collaboration of Adobe Systems, Aldus Corporation, and Apple Computer. Prior to this, graphic designers worked with manual methods, such as paper, scissors, and glue. The introduction of DTP had a significant impact on organizational structures and established a new central role for the DTP publisher—a consolidation of various roles, such as graphic designer, typographer, typesetter, and secretary—within an organization. The time required for many DTP processes was drastically reduced from several hours or even days to minutes or even seconds. Aldus Corporation—the company behind the DTP application PageMaker—was acquired by Adobe in 1994, and PageMaker served as the foundation for Adobe InDesign, released in 1999. Today, InDesign can be licensed either as a standalone application or as part of a bundled software package. Adobe applications, including InDesign, are still considered the industry standard in the field of DTP. Furthermore, with rapid technological advancements, not only have the tools available for content creation changed significantly, but the range of media through which messages can be communicated has also multiplied.

3. Chapter 2. The Future of Desktop Publishing

   Ennis Gündoğan

   Abstract

   Today, content can be created not only on desktop devices but also on alternative platforms. Adobe Photoshop and Illustrator are available for the iPad as mobile applications, as well as web applications. With Adobe Sensei and the Firefly technology based on it, new possibilities have emerged in AI-powered image generation. Currently, three new Firefly models are available: Firefly Image 3 integrated into Photoshop and InDesign, Firefly Vector Model integrated into Illustrator, and Firefly Design Model integrated into Adobe Express. In view of previous AI-related developments, it can be assumed that automation and AI will play an even greater role in the future of DTP.

4. Chapter 3. Automation

   Ennis Gündoğan

   Abstract

   Automation plays a crucial role in securing an organization’s position in the market and maintaining its future competitiveness. Depending on the industry, automation can be defined and categorized in various ways. In general, automation mechanisms can be divided into two types: full automation and partial automation. In full automation, a process is carried out entirely by a machine, whereas in partial automation, a manual task is supported by a machine. In the field of automation, depending on the degree of automation, the use of AI, and process complexity, four automation technologies can be identified or classified: RPA, Cognitive Process Automation (CPA), digital assistants, and autonomous agents. While RPA uses software to operate existing application systems within a company to automatically perform structured tasks, adaptive CPA systems can recognize data patterns, enabling their use in complex and dynamic process structures. Digital assistants or voice assistants are capable of capturing natural human dialogues, processing them, and providing answers to complex questions. Autonomous agents refer to complex software systems that can make independent decisions and initiate further processes.

5. Chapter 4. The Future of Automation

   Ennis Gündoğan

   Abstract

   AI-driven systems will play an increasingly significant role, and developments in machine learning will become progressively more sophisticated over time. Machines will continue to be fine-tuned by humans until they have accumulated sufficient experience to operate fully autonomously. The growing number of software-based automation processes has sparked a debate about the potential for substantial job losses. However, these concerns are currently unfounded, as not every automation opportunity is being fully exploited today. Furthermore, the division of tasks between humans and machines remains flexible. Automation technologies will not lead to job losses, but rather increase productivity within organizations. It is not jobs that are being rationalized, but tasks. As a result, skilled professionals will be able to take on more demanding responsibilities elsewhere. Additionally, systems supported by automation will always require human oversight. This leads to the conclusion that professionals will need to continue their education in the future in order to perform these new types of tasks.

6. Chapter 5. Automation of Artwork Processes

   Ennis Gündoğan

   Abstract

   Automation comes into play when processes follow a certain repetitive pattern. The range of automation options within artwork processes extends from small tools, such as scripts integrated into DTP software, to complex software infrastructures that enable automated publishing. Many current DTP applications offer various interfaces and extension options for developers. As with all forms of automation, the main objectives in the DTP domain are to reduce company costs and improve final outcomes through standardization and error reduction, as well as to relieve employees of labor-intensive and monotonous tasks. In contrast to creative design processes, humans are inefficient when performing repetitive tasks. These include, for example, copy-paste activities or the repeated production of graphic assets. Ideally, the structural shift from manual to automated processes is accompanied by a sense of purpose. By involving employees in the change process and transparently communicating the rationale behind these changes, not only is the fear of change reduced, but employee motivation is also increased through the opportunity to participate. Structural change is not about layoffs, but rather about alleviating workloads. The development of DTP automation solutions is variable and depends on how business processes are structured and managed within each company.

7. Chapter 6. Extensible Markup Language (XML)

   Ennis Gündoğan

   Abstract

   With the markup language XML, InDesign enables a strict separation of layout and text. A particularly powerful XML feature in InDesign is the ability to assign previously imported or InDesign-created XML tags to predefined formats such as paragraph styles, character styles, and table styles. This makes it possible to populate entire layout templates with fully formatted content in a very short time. During an XML import, an Extensible Stylesheet Language Transformation (XSLT) file specifies, among other things, the order in which the XML elements should be sorted if the order of the tags in InDesign differs from that of the XML elements. To check for occurrences of specific elements, attributes, and entities in an XML file, Document Type Definition (DTD) files are used. These thus define the expected XML structure of an XML file. Another XML-related InDesign feature is the so-called InDesign Markup Language (IDML), a markup language introduced by Adobe to describe entire InDesign documents in XML format. In theory, this makes it possible to edit or even create an entire InDesign document using XML. Based on IDML are the so-called InDesign snippets in the IDMS file format. A snippet is an XML file that describes an InDesign asset. Any InDesign asset can be exported as a snippet. Likewise, snippets can be imported into an InDesign document and edited as desired.

8. Chapter 7. Scripts

   Ennis Gündoğan

   Abstract

   Many Adobe applications can be controlled using scripts written in JavaScript (JS) based ExtendScript—Adobe’s proprietary scripting language—AppleScript, or Visual Basic Script (VBScript). It is possible to replicate virtually any UI interaction and function of a supported application through scripting. The range of possible applications extends from simple operation of menu elements to the generation of complex graphics on the DTP application’s canvas, and even to the automation of repetitive artwork processes in daily workflows. Scripts can be provided to users as standalone script files to be loaded into the respective Adobe application, but they can also be integrated with other Adobe technologies.

9. Chapter 8. Global Regular Expressions Print (GREP)

   Ennis Gündoğan

   Abstract

   Another widely used and comprehensive feature in InDesign, particularly in the context of automation and scripting, is GREP. GREP extends the traditional text search by enabling the identification of desired text patterns using regular expressions and wildcards. What makes GREP unique is that search and replace operations can be applied not only to text but also to formatting. For example, it is possible to search for a text pattern in a specific font and replace it with both different text and a different font. GREP can also be controlled via scripts, making it suitable for use in both partial and full automation workflows.

10. Chapter 9. C++ Plugins

    Ennis Gündoğan

    Abstract

    Several Adobe applications, including InDesign, Photoshop, and Illustrator, offer a Software Development Kit (SDK) that enables the respective application to be extended with a plugin written in the C++ programming language. The main difference between scripts and C++ plugins is that scripts control existing functions within the respective Adobe application, whereas C++ plugins can be used to implement new functions based on the application's existing capabilities. A key advantage of C++ plugins is performance, as this low-level programming language executes faster than, for example, a scripting language. The Adobe Developer Console serves as a central hub that, in addition to the SDKs, provides extensive documentation and code samples, which are essential for the development of C++ plugins, among others.

11. Chapter 10. Common Extensibility Platform (CEP)

    Ennis Gündoğan

    Abstract

    CEP enables the development of extensions using HTML, Cascading Style Sheets (CSS), and JS, which can be seamlessly integrated into the UI of Adobe applications, for example as a panel. The power of CEP lies in its support for Node.js and ExtendScript. The interplay of these technologies makes it possible to implement a wide range of software projects in the context of DTP automation. CEP technology not only enables interaction between a CEP extension and a host application, but also communication of host applications and CEP extensions with each other.

12. Chapter 11. Unified Extensibility Platform (UXP)

    Ennis Gündoğan

    Abstract

    UXP is a technology introduced by Adobe in 2018 that enables the extension of CC applications based on JS, HTML, and CSS. Since then, this technology has been continuously developed. UXP can be seen as a modern replacement for CEP. A key difference compared to CEP is the efficient capability for direct interaction with an Adobe application using the respective application APIs, whereas CEP requires an additional layer to transmit a command to the host. Furthermore, UI elements created with HTML and CSS are converted into native UI elements of the respective host, resulting in additional performance advantages.

13. Chapter 12. Adobe InDesign Server

    Ennis Gündoğan

    Abstract

    Adobe InDesign Server is well-suited for processing complex layout templates and the mass generation of graphic assets. This application is not included in the Creative Cloud product family, but can be licensed separately by enterprise customers. Within the Adobe product family, InDesign is the only application for which a server variant exists.

14. Chapter 13. Other Tools

    Ennis Gündoğan

    Abstract

    For simpler automation tasks, Adobe provides a variety of features within its applications. These are primarily aimed at users without programming experience and can be configured and used with minimal effort. Such features include actions in Photoshop and Illustrator, as well as the Script Event Manager and Image Processor in Photoshop.

15. Chapter 14. Client-Server Communication

    Ennis Gündoğan

    Abstract

    It is advisable to handle the majority of processes server-side and to perform as little data processing and automation as possible on the client, so that users do not experience any performance drawbacks. Nevertheless, when implementing a software infrastructure for DTP automation, it is always necessary to critically assess the effort required by each process in order to determine whether it is better suited for the client or the server. Layouts and graphic assets that are used repeatedly and differ primarily in content rather than design can be provided as templates on a central file server for multiple use.

16. Chapter 15. Databases and Application Systems

    Ennis Gündoğan

    Abstract

    For content creation within the scope of DTP, data can be sourced not only from a single data source but also from various other sources such as databases. The connection between these data sources and the layouts can be established via a middleware or a plugin within the DTP application. If multiple data sources are used in the context of DTP automation, the Extract-Transform-Load (ETL) process may be considered. Furthermore, all software activities can be recorded in files or databases in the form of logs and later analyzed and used both for software optimization and for statistical purposes. If developers identify a specific pattern within the logs, this pattern can be defined as a new automation rule.

17. Chapter 16. Integration with Process Management Applications

    Ennis Gündoğan

    Abstract

    Automation applications can be triggered not only by users but also by other applications. A status change in a workflow within a process management application can simultaneously be defined as a trigger for an automated process. This is particularly suitable for automated artwork processes that are time-intensive, such as the generation of hundreds of graphic assets tailored to a specific project, which can be executed overnight.

18. Backmatter