2020 August Release

Fabasoft Cloud 2019 April ReleasePermanent link for this heading

Find out more about new features and improvements in the Fabasoft Cloud 2019 April Release.

PurchasePermanent link for this heading

The purchase management enables you to conduct an efficient, digital purchase process. With the help of forms and processes, the purchase management can be adapted to the needs of your organization.

Note: Available in the Fabasoft Cloud Superior (must be unlocked by Fabasoft Cloud Support).

The purchase process differs from organization to organization. Therefore, you have to define the required BPMN processes by yourself.

Basically, the following applies: The purchase workflow begins with an employee's requirement request and goes through defined approvals by superiors. If the appropriate permissions are present, then the order can be accomplished by the purchasing department. With the goods receipt the delivery note is stored for the order. The invoice is also stored for the order.

In particular, the following activity definitions can be used for the purchase process:

  • Prepare Requirement Request
  • Approve Requirement Request
  • Approve Requirement Request (Specialist Department)
  • Edit Requirement Request
  • Edit Order
  • Further Information Required

The processing status of the requirement request can be used for case distinctions in the purchase process:

  • In Preparation
  • For Approval
  • Approved
  • Discarded
  • Declined
  • In Stock
  • Ordered

Change and Release ManagementPermanent link for this heading

The change and release management enables you to create and manage change processes. This allows carrying out adaptations to an IT infrastructure in a controlled, efficient and risk-minimized manner.

In addition, problem records can be managed and processed using a problem management process.

Note: Available in the Fabasoft Cloud Superior (must be unlocked by Fabasoft Cloud Support).

A typical change process includes the following activities:

  • Approve Request for Change
  • Release Planning
  • Prepare Release
  • Approve Release
  • Scheduling
  • Deployment
  • Review Release Package
  • Close Request for Change
  • Request for Change Closed

A typical problem management process includes the following activities:

  • Classify Problem Record
  • Edit Problem Record
  • Review Problem Record

Top and Title BarPermanent link for this heading

In the top bar the cloud graphic has been removed as background for your organization logo. If the organization administrator has defined a logo but no background color, the top bar is displayed gray because most logos are designed for a light background. The home button is now on the far right.

In the title bar, you will find the breadcrumbs of the currently opened hierarchy. If you navigate in a widget, all other widgets of the same level are display as tabs.

When you navigate in the worklist, you go directly to the “To Do” list. If you click on "Worklist" in the breadcrumb, all widgets of the worklist are displayed.

Sending an E-Mail to Team MembersPermanent link for this heading

To simplify collaboration even further, e-mails can be sent directly from Teamrooms to the team. The “Send” > “Send E-Mail to Team Members” context menu command is available for Teamrooms and for objects assigned to Teamrooms. When using the context menu command on objects, they are added as links to the e-mail.

For the simple selection of recipients, they can be determined via their role in the Teamroom and filter criteria.

Meta Data in Microsoft ExcelPermanent link for this heading

To have metadata available in a Microsoft Excel worksheet, the values of selected fields can be inserted on a separate worksheet. In this way, the values can be referenced in your own worksheets.

To do this, you can enable the option Use Fields in Microsoft Excel on the “Contents” tab. The “Define Fields” button allows you to define the available fields and the name of the worksheet on which the values of the fields are to be included.

WorkflowPermanent link for this heading

The workflow provides following new features:

  • If you assign or change your own names for process elements in the BPMN editor, these are saved in the current user language. For users with different language settings, you can store the translated names on the “Translations” tab. In this way, the name is displayed in the BPMN editor and also in the worklist according to the language settings of the respective user.
  • The dialog for ad hoc processes has been revised. In the left-hand area, you can define the activity and optionally define your own display name for the activity. You can define the participants in the right-hand area.
    Using the “Show Deadlines” button, you can define time limits for the ad hoc process.
    In the lower area you will find the process diagram. You can use the “Apply” button to define several activities. You can determine the position in the process using the plus symbols.
  • Two new abstract participants are available in the workflow: “Property of the File of the Object” and “Role by Property of the File of the Object”. The participant can thus also be determined using properties of the object's file.
  • To make it easier to terminate processes that are no longer relevant, the “Change State” button is available for the respective object on the “Processes” tab in the complete view of the process. This allows you to change the state to “In Progress”, “Suspended”, “Completed” or “Aborted”.

Common ImprovementsPermanent link for this heading

  • An opened property editor can be moved to a new window via the “Open in New Window” button. This allows you to continue working in the previously hidden background.
  • In the case of videos, the second at which the preview image is generated can be specified on the “Content” tab in the Generate Thumbnail at Second field.
  • For download formats of images DPI can be defined additionally.
  • If you change the context (domain and user account) in Microsoft Office, the context is also changed in the Fabasoft Cloud Client and vice versa.
  • The With Read Access Visible to All Members field of a Teamroom defines whether all team members of the team are allowed to see the members with read access. If the setting is disabled, the team members with read access are only visible for members with "Full Control". Note that disabling this setting also restricts other use cases:
    • Only team members with “Full Control” have access to the “Team” action and can start processes.
    • Events can generally be deactivated for team members who are not allowed to see the team. Otherwise, only events will be displayed that do not allow conclusions to be drawn about team members with read access.
    • Team members with read access cannot use annotations, signatures, processes or comment on news feeds.
    • Team members with read access cannot be selected as participants in processes.
    • Team members with read access cannot create public links.