App Card

When you navigate to the Workspace, you will be directed to the default directory named 'Home.' On this screen, you will find folders, dashboards, apps, and notebooks presented in a card view format. If you prefer a different layout, you can easily switch to a grid view.

This article provides an in-depth exploration of the features and details of the app cards. The above screenshot shows 3 apps in card view. Let's discuss their details :

Star Icon (Favorite)

Favorites are indicated by a star icon displayed in the top left corner of the app card. The icon is white by default, but once the user clicks on it, it turns Yellow and the app will be marked as a favorite. In the example below, the app named 'Synyasa Demo App' is marked as a favorite while the other two apps are not marked as favorites.

Title

This indicates the name of the app that was given by the user while creating the app or while updating the app name.

Template Name

Right below the App title, the app template name is shown. This template is only selectable and editable at the time of creation. After the app is created, users cannot modify this field. In the above screenshots, the template name is shown as 'Adobe Analytics Adapter' for all three apps.

Created

This field displays the app creation timestamp.

App Icon

The default icon is based on the selected app template, as shown in the screenshot above. This icon can be overridden with a custom icon within the app's Overview section.

Environment Details

Next to the app icon, the card shows sections for development and production. The app card displays the last Job status of each workflow. Let's discuss the details common to both environments first.

Common Details:
- Last Job Run: The card shows when the last job was run. If it displays "N/A," it means no job has been run since the app was created.
- Job Status: The card indicates whether the last job was successful, failed, or aborted. Here is the list of different Job statuses:
  - Job Failed: - The red triangle icon () is displayed if the last job failed for the app within the specified section.
  - Job Passed: - The green tick icon () is displayed if the last job succeeded for the app within the specified section.
  - Job Aborted: - The yellow pause icon () is displayed if the last job is aborted for the app within the specified section.

Examples:

- - In the screenshot below, the app named 'App Card Demo' shows a green tick ()with the last run timestamp, indicating that the last job was successful and includes the run time
  - The app named 'No Run Demo App' shows no running status and 'Last Run' as N/A, meaning no job has ever been run in the Development environment for this app.
  - The app named 'Syntasa Demo App' shows a paused icon (), indicating an aborted job.

Development Environment Details:
- Interactive Mode: When enabled in the development environment, it is represented by a helmet icon () next to the Development text. You can check the interactive mode icon in the below screenshot for the app 'Demo 1st App'.
Production Environment Details:
- Next Run: If any job is scheduled in the production environment, the card shows the next run time under the field 'Next Run'; otherwise, it shows "N/A."
- If the production section is shown greyed out, it means the app has not yet been deployed to production.

Delete

When hovering over the app card in Syntasa, the user will notice a red x icon () which allows you to delete the app.

Note: Before proceeding with deletion, the system checks if the app is currently in Interactive Mode. If the app is actively running in Interactive Mode, deletion will not be permitted.

App Menu

On the app card, users have multiple options accessible through the triple-dot icon.

Let's understand each option shown under the triple-dot icon menu:

Overview: Selecting this will take the user to the 'Overview' screen where basic app details such as name, key prefix, and event store can be checked. Users can also update details like name, description, and app icon.
Journal: Selecting this option will take users to the Journal screen, which shows all the snapshots taken for an app.
Development: The Development Workflow has four different screens:
- Workflow: This takes the user to the development workflow canvas where new configurations can be tested and ensured they are functioning as intended before being deployed to production.
- Operations: The operations screen provides details about ad-hoc job processing and offers the ability to modify job settings.
- Dashboards: This screen allows third-party visualization applications to be embedded within the app. If no dashboard screen is attached, a "No Dashboards Exist" message will be displayed with a "+" icon. By using this "+" icon, users can add third-party visualizations.
- Dependencies: This screen displays the development datasets that are feeding into the app and the development datasets consuming the data derived from the app.

Production: The purpose of the production environment is to execute deployed configurations and enable the scheduling of recurring jobs. Production functionality becomes available only after an app has been deployed for the first time. This section is divided into four parts:
- Workflow: This canvas is the default screen that appears when clicking on an app card. It will show you the last deployed version.
- Operations: The operations screens provide details about ad-hoc job processing and offer the ability to modify job settings. You can check the scheduled jobs on this screen.
- Dashboards: The dashboard screen allows third-party visualization applications to be embedded within the app if no dashboard screen is attached there then the 'No Dashboards Exist message' will be displayed with the "+" icon. By using this + icon users can add third-party visualization.
- Dependencies: The dependencies screen displays the production datasets that are feeding into the app and the production datasets consuming the data derived from the app.
Export: By using the export feature, users can download an existing app. Selecting this option will redirect you to the screen where you can start the export process.

{[{category.name}]}