Release Information - Version 1.10

Table View for Event Class / Type Field

When selecting the event class and type in for example the Event mapping, one can now open a table where it can be selected easier from.

event class and type 1

And the table is presented in the similar way as done in the 3DEXPERIENCE™ application.

event class and type 2

Parent Job Reference Type

Jobs can be linked together with a parent-child relationship. This kind of relationship may have different meaning, such as:

  • The child job is created as part of the execution of the parent job

  • It is a retry of a previous job execution

  • It is a reply to another job

The relationship type is indicated better in the UI now.

parent child link

Installing Older Version of a Marketplace Extension

Exporting the settings for a marketplace extension now includes the version of the extension itself within the exported data.

That information is used when importing the settings at a later time, e.g. if the settings are imported and the extension is NOT installed, or the settings are imported using the FORCE flag, then the version of the extension as specified in the import will be installed.

Improved Performance on the Dashboard Page

The first screen, the dashboard page, could in some situations take long time to load, which now is being fixed.

Java Script Configurations

The changes related to Configurations implemented in JavaScript are described in the sub-chapters below.

Module Support

Support for modularizing the configurations using the import/export keywords are now available per default for all JavaScript configurations.

For example in one configuration you could export a function, constant or class that is imported from another configuration.

See the example below:

sap/library.js
const myFunc = (name) => `Hello ${name} !`;

export { myFunc as hello };
sap/use-case.js
import { hello } from 'sap/library';

console.log(hello('TIF'));

This allows you to implement the code in a similar way as traditional JavaScript applications are developed and structured.

PDF API - Title and Ending Pages

The PDF service allowing you to convert Office documents into PDF files now supports adding title and/or ending pages.

Example code extracted from the Marketplace extension called "TIF Examples".

const titlePage = getBinaryResource(
    'tif/examples/data/TitlePage.txt',
    'title_page.docx');
const pdfFile = context.localFileAPI().create('test.pdf');
const result = context.converterAPI()
    .convertToPDF()
    .inputFile(docFile)
    .properties()
    .add('hello', 'world')
    .add('DOC_NAME', 'TESTING-123')
    .add('DOC_TYPE', 'SPECIFICATION')
    .and()
    .pdf()
    .and()
    .merge() (1)
    .addTitlePage(titlePage) (2)
    .and() (3)
    .watermark()
    .addText()
    .text('Testing Watermark')
    .rotate(-45)
    .fontSize(72)
    .fontName('Arial')
    .fontColor('red')
    .pageLocation('all-except-first-page')
    .and()
    .and()
    .perform(pdfFile);
1 Enter the merge configuration
2 Adding the title page file, which is a LocalFile
3 Complete the merge configuration block
The PDF converter API requires a separate license to be used.

Terminate Code Execution

A new method on the Context API has been added to allow terminating the ongoing Job execution.

It will immediately terminate the script at the line it was called, not other lines of code will be processed.

This method is simply invoked like:

context.exit();

Fixed Bugs

Below is the list of fixed bugs as of this release.

Issue No Description

608

Files dialog on job page did not show special characters correctly