Part 4: The Inbox

Overview

With the core services and components in place, we'll now interface with the ProcessMaker API.

Completed code: live examplearrow-up-right / download examplearrow-up-right

Step 1: Environment Details

Ensure you have the subsequent details ready for this section:

  • Client ID

  • Client Secret

  • FQDN for your ProcessMaker installation

  • OAuth Token URL

  • OAuth Redirect URI

  • OAuth Authorization URL

You can see what a sample environment.ts file looks like below. This is where you will add the above information.

chevron-rightenvironment.tshashtag
export const environment = {
	production: false,
	apiDomain: 'localhost',
	apiPath: '/api/1.0',
	apiProtocol: 'http://',
	clientId: '19',
	clientSecret: 'Psn9cxcGFKO1GO4ZZ9TgOhQtAjt0Wmzjc58vw8Lq',
	oauthUrl: 'http://localhost/oauth/token',
	redirectUri: 'http://localhost:4200/#/oauth/callback',
	oauthAuthorizeUrl: 'http://localhost/oauth/authorize',
	customCss: false,
	calcProps: true,
};

Step 2: TasksComponent

The TasksComponent relies on the ScreenComponent, which we'll address in the subsequent section. We'll omit it for now and reintroduce it when we're set to render the form.

Template

chevron-rightapp-tasks.component.htmlhashtag

Typescript

chevron-rightapp-tasks.component.tshashtag

Step 3: Update the Router

Integrate the new components and their respective paths into the router. The following code demonstrates how to import these components and establish a route for the inbox view.

chevron-rightapp-routing.module.tshashtag

Step 4: Update AppModule

Now we just need to incorporate the TasksComponent into the AppModule declaration.

chevron-rightapp.module.tshashtag

Review

If you are following along with the tutorial, you should now be able to see your tasks, in your new Angular Inbox!

Angular Inbox for ProcessMaker

Next Steps

Part 5: The Screen & Form Elementschevron-right

Last updated