Important Notice

This public repository is read-only and no longer maintained. For the latest sample code repositories, visit the SAP Samples organization.

SAP Field Service Management Crowd Partner Portal

Partner Portal enables SAP FSM Crowd service partners to:

• maintain their technicians data (skills, certificates, contact information, etc.)
• upload and maintain company information (e.g. upload certificate documents)
• manage service assignments (accept/reject, assign, release, close)

This repository contains a reference implementation. It is an example on how to use our public APIs. It helps crowd owners to offer their service partners a customized experience.

Table of contents

• Partner Portal
  • Table of contents
  • Requirements
  • Installation
  • Configuration
  • Logging
  • Stats
  • Known issues
  • How to obtain support
  • Contributing
  • To-Do (upcoming changes)
  • Architecture
  • SAP APIs being used
  • License

Requirements

• Node.js (find required version in the .nvmrc files)
• @angular/cli installed globally (link)
• Valid credentials for the SAP Customer Experience - Service Cloud

Installation

Put your Google Maps API key and channel into partner-portal/frontend/src/app/service-area-module/service-area.module.ts file.

Replace fake client secret ("partner-portal-test") with your client secret in start:local script.

Run the application backend:

> cd backend
> npm install
> npm run start:local:de

Then start the UI:

> cd frontend
> npm install
> npm run dev

The webpage will be accessible under:

http://localhost:4200

Configuration

The application can be started with configuration files as parameters. Those files are located under /backend/config. Create new configurations as needed.

Logging

You may extend LoggerService class with a functionality to report BFF's logs to a 3rd party solution, like ELK or Loggly.

Stats

You may use StateEffects class on frontend to report app events (based on NgRX actions) to some analytics tools like Google Analytics or Countly.

Known issues

None

How to obtain support

There is no support offered for this project. The project serves as reference implementation on how to use our APIs.

Contributing

Contributions are not supported. Since this is just example code.

To-Do (upcoming changes)

Architecture

In the repository, there are two folders:

1. frontend, containing the user interface
2. backend, the application backend

(Following the FBB pattern.)

The application itself is being executed as a stateless client. There is only ephemeral data being processed in the frontend.

The following libraries are utilized:

• Frontend
  • Angular
  • ngrx
  • Karma + Jasmine for tests
  • Angular CLI as build manager
• Backend
  • express.js
  • Mocha for tests
  • gulp as build manager

SAP APIs being used

The following public APIs are being utilized:

• Branding Settings Service (docs)
• Crowd Service (docs)
• Crowd Partner Dispatch Service (docs)
• OAuth2 (endpoint https://de.coresuite.com/api/oauth2/)

License

Copyright (c) 2020 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.