open-index/open-npm huggingface dataset:
npm package: @process-engine/dynamic_ui_core
Description: Businesslogic of dynamic ui
Author: Robin Lenz
Latest version: 1.8.0
Deprecated: This package is no longer maintained.

# dynamic_ui_core

This bundle holds the basic components to render simple User- and ManualTasks
inside BPMN-Studio.

## Configure and Display simple UserTasks

To configure a UserTask simply click on it in the designer of BPMN-Studio.
The PropertyPanel will show the current configuration, including the form fields.

![Simple UserTask 1](./docs/images/SimpleUserTask(1).png)

To add a new form field click the "+" button on the PropertyPanel.

![Simple UserTask 2](./docs/images/SimpleUserTask(2).png)

After adding a new form field you can configure it. In this example we are
working with a text form field.

![Simple UserTask 3](./docs/images/SimpleUserTask(3).png)

To configure a dynamic default value you have to add it like this:

`${token.current.<path-to-value-here>}`

or

`${token.history['<id-of-node-here>'].<path-to-value-here>}`

To display that UserTask now

- save the diagram
- deploy it to the ProcessEngine
- run it
- click on the task in the Live Execution Tracker

![Simple UserTask 4](./docs/images/SimpleUserTask(4).png)

You can now see your configured UserTask.

![Simple UserTask 5](./docs/images/SimpleUserTask(5).png)

### Example Process

For a full example of a process with a configures UserTask see:

[Example UserTask Process](./docs/processes/SimpleUserTask.bpmn)

## Configure and Display confirm UserTasks

To configure a UserTask to use the "confirm", control add the `preferredControl`
key with the value `confirm` to the properties of the UserTask.

![Confirm UserTask 1](./docs/images/ConfirmUserTask(1).png)

The confirm control expects at least one boolean ("Truth Value") form field.
It will not render the first boolean form field configured in the UserTask and
instead use it to fill it with the information about the button click.

To configure the boolean form field simply click on the "+" button and select
"Truth Value" in the dropdown. There is no label needed for this form field since
it doesn't get rendered anyway.

![Confirm UserTask 2](./docs/images/ConfirmUserTask(2).png)

You can now again

- save the diagram
- deploy it to the ProcessEngine
- run it
- click on the task in the Live Execution Tracker

You can now see the configured confirm UserTask.
Since it is a confirm UserTask the DynamicUi rendered some extra buttons.

![Confirm UserTask 3](./docs/images/ConfirmUserTask(3).png)

Clicking on "Proceed" will lead to a `true` in the first boolean form field of
the UserTask.

Clicking on "Decline" will lead to a `false` in the first boolean form field of
the UserTask.

### Example Process

For a full example of a process using the confirm control see:

[Example Confirm UserTask Process](./docs/processes/ConfirmUserTask.bpmn)
npm package: @process-engine/iam
Description: Contains the process engines' IAM related functions.
Author: 5Minds IT-Solutions GmbH & Co. KG
Latest version: 1.7.4
Deprecated: This package is no longer maintained.

# Identity and Access Management - IAM

Contains the implementation of the
[essential-projects IAM contracts](https://github.com/essential-projects/iam_contracts)
interfaces.

## Purpose

The ProcessEngine uses IAM for performing authorization related requests.
The contracts found in `essential-projects/iam_contracts` provide a template for this.

Two services are available:

1. IamService

   Used for interaction with the authority.
   `ensureHasClaim` allows to check if a given identity has a given claim.

2. IdentityService

   A service that knows how to transform a given token (e.g. JWT) to an
   identity that the authority can understand.

**Usage Example:**

The easiest way to get familiar with the idea is to look at an example; this
will illustrate the use of and the interaction between the IamService and the
IdentityService:

```ts
const identityService: IIdentityService = new IdentityService();
const iamService: IIAMService = new IAMService(new HttpClient(), identityService, this.config.introspectPath);

// Get the identity for a given JWT token.
const token: String = "Place JWT Token here";
const identity: IIdentity = identityService.getIdentity(token);

// Will result in:
//
// 1. An UnauthorizedError HTTP Status code, if the identity is not logged in at the authority.
// 2. A ForbiddenError HTTP Status code, if the identity does not have the given claim.
// 3. Nothing, if the identity has the given claim.
iamService.ensureHasClaim(identity, 'allowd_to_read_data');

// Place protected code here.
(...)
```

## Usage

Using IAM is simple. You can use `ensureHasClaim` to verify any claim for any identity.

You'll get one of the following results:

1. Get an Unauthorized Error

   A 401 will be thrown, if the identity is not known to the authority or the
   token is invalid/expired/etc.

2. Get a Forbidden Error

   A 403 will be thrown, if the given identity does not have the given claim.

3. Get Nothing, if the identity has the given claim.

   A 204, which indicates that the identity has the given claim.

## Configuration

The IamService needs some minor configurations; it needs to know:

1. Its authority.
1. The client secret.
npm package: @process-engine/process_engine_contracts
Description: The referencable contracts for the whole ProcessEngine.
Author: 5Minds IT-Solutions GmbH & Co. KG
Latest version: 47.1.0
Deprecated: This package is no longer maintained.

# process_engine_contracts

This project contains the contracts used for interacting with the ProcessEngine.

## Namespaces

The contracts are split into two main Namespaces:

### Model

This Namespace contains all components that describe a ProcessModel, such as
Activities, Gateways, Events and so forth.

Also, it contains the interfaces for the `BpmnModelParser`.

The interfaces and types are grouped into folders, each reflecting a single
category:
- `activities`: Contains FlowNodes such as ScriptTasks, ServiceTasks,
CallActivities, etc.
- `base`: Contains base classes used across the namespace
- `event_definitions`: Contains definitions for various event types,
used by the classes stored in `events`
- `events`: Contains types for all kinds of Events supported by the BPMN
specs
- `gateways`: Contains types for all kinds of Gateways supported by the
BPMN specs
- `type_references`: References are used by `events` and `event_definitions`
and contain infos about things like messages, signals, etc.
- `types`: Contains types for the elements that are common to all BPMNs, such as
Participants, Collaborations, Annotations, etc.

### Runtime

This namespace contains the interfaces and types for all the services
and repositories that provide access to the ProcessEngine.

The interfaces contained are grouped into the following categories:
- `engine`: Contains interfaces for services and handlers that manage the
execution of ProcessModels
- `messages`: Contains definitions for internal messages used for communication
with the EventAggregator
- `storage`: Contains interfaces for services and repositories used for accessing
the persistence layer
- `types`: Contains definitions for commonly used types, such as `ProcessToken` or
`FlowNodeInstance`
npm package: @process-street/jquery-ui
Description: A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.
Author: jQuery Foundation and other contributors
Latest version: 1.12.1

# [jQuery UI](http://jqueryui.com/) - Interactions and Widgets for the web

jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Whether you're building highly interactive web applications, or you just need to add a date picker to a form control, jQuery UI is the perfect choice.

If you want to use jQuery UI, go to [jqueryui.com](http://jqueryui.com) to get started, [jqueryui.com/demos/](http://jqueryui.com/demos/) for demos, [api.jqueryui.com](http://api.jqueryui.com/) for API documentation, or the [Using jQuery UI Forum](http://forum.jquery.com/using-jquery-ui) for discussions and questions.

If you want to report a bug/issue, please visit [bugs.jqueryui.com](http://bugs.jqueryui.com).

If you are interested in helping develop jQuery UI, you are in the right place.
To discuss development with team members and the community, visit the [Developing jQuery UI Forum](http://forum.jquery.com/developing-jquery-ui) or [#jqueryui-dev on irc.freenode.net](http://irc.jquery.org/).


## For Contributors

If you want to help and provide a patch for a bugfix or new feature, please take
a few minutes and look at [our Getting Involved guide](http://wiki.jqueryui.com/w/page/35263114/Getting-Involved).
In particular check out the [Coding standards](http://wiki.jqueryui.com/w/page/12137737/Coding-standards)
and [Commit Message Style Guide](http://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines).

In general, fork the project, create a branch for a specific change and send a
pull request for that branch. Don't mix unrelated changes. You can use the commit
message as the description for the pull request.

For more information, see the [contributing page](CONTRIBUTING.md).

## Running the Unit Tests

Run the unit tests manually with appropriate browsers and any local web server. See our [environment setup](CONTRIBUTING.md#environment-minimum-required) and [information on running tests](CONTRIBUTING.md#running-the-tests).

You can also run the unit tests inside phantomjs by [setting up your environment](CONTRIBUTING.md#user-content-environment-recommended-setup).
npm package: @process-street/ui-select
Author: http://github.com/angular-ui/ui-select/graphs/contributors
Latest version: 0.19.10

# AngularJS ui-select [![Build Status](https://travis-ci.org/angular-ui/ui-select.svg?branch=master)](https://travis-ci.org/angular-ui/ui-select) [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/angular-ui/ui-select?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)


AngularJS-native version of [Select2](http://ivaynberg.github.io/select2/) and [Selectize](http://brianreavis.github.io/selectize.js/). [http://angular-ui.github.io/ui-select/](http://angular-ui.github.io/ui-select/)

[Getting Started](https://github.com/angular-ui/ui-select/wiki/Getting-Started) 

- [Examples](http://angular-ui.github.io/ui-select/#examples)
- [Examples Source](./docs/examples)
- [Documentation](https://github.com/angular-ui/ui-select/wiki)

## Latest Changes

- Check [CHANGELOG.md](/CHANGELOG.md)

## Features

- Search, Select, Multi-select and Tagging
- Multiple Themes: Bootstrap, Select2 and Selectize
- Keyboard support
- No jQuery required (except for old browsers)
- Small code base: 4.57KB min/gzipped vs 20KB for select2

For the roadmap, check [issue #3](https://github.com/angular-ui/ui-select/issues/3) and the [Wiki page](https://github.com/angular-ui/ui-select/wiki/Roadmap).

## Installation Methods

### npm
```
$ npm install ui-select
```
### bower
```
$ bower install angular-ui-select
```

## Development

### Prepare your environment
* Install [Node.js](http://nodejs.org/) and NPM (should come with)
* Install global dev dependencies: `npm install -g gulp`
* Install local dev dependencies: `npm install` in repository directory

### Development Commands

* `gulp` to jshint, build and test
* `gulp build` to jshint and build
* `gulp test` for one-time test with karma (also build and jshint)
* `gulp watch` to watch src files to jshint, build and test when changed
* `gulp docs` build docs and examples

## Contributing

- Check [CONTRIBUTING.md](/CONTRIBUTING.md)
- Run the tests
- Try the [examples](./docs/examples)

When issuing a pull request, please exclude changes from the "dist" folder to avoid merge conflicts.