onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

btp-user-role-request

The files published for two Japanese blog posts on registering a BTP user with SAP Build Process Automation: three .mtar archives and a README that links the posts.

The README is the index to the two posts the repository was created for: the first automates registering a BTP user with SAP Build Process Automation, the second builds an Action from an API its author wrote themselves. Beside it are three files and no description of them, named BTP user role request_1.0.7.mtar, CF command API_1.0.0.mtar and Manage users API_1.0.1.mtar, so which one carries the process and which the actions is not written down here. The README ends with the question its author posted on SAP Community while working on the second post, 'Build Process Automation: Invalid Argument: Type of destination must be HTTP'.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
BTP/BAIP
Demonstrates
Process automationBTPProcess automationcapabilityModelling and running a business process: the process flow, the forms people fill in, decision tables, bots for repetitive steps, and dashboards over the instances that run. Starting a process from an application and reacting to it is [workflow integration](capability:workflow-integration), and the screen a person approves a task on is [task and approval UIs](capability:task-uis).
Requires
SAP Build Process AutomationSAP Build Process AutomationartifactBoth posts the repository was created for build their automation in SAP Build Process Automation: the first the BTP user registration, the second an Action from an API of its own.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

The repository publishes no licence, so reusing the files needs the author's permission. Nothing here says what each file contains, and the two posts they were published for are in Japanese.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
does not say

Connections2

README

quoted from miyasuta/btp-user-role-request, read
miyasuta/btp-user-role-request/README.mdOn GitHub

btp-user-role-request

Process Automation

This repository is created for the following blog posts.

  1. SAP Build Process AutomationでBTPのユーザ登録を自動化する
  2. SAP Build Process Automation: 自作のAPIからActionを作る

For the second blog post, there is a issue which I posted a question on SAP Community.

, read

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/btp-user-role-requesttree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domainbtp, process-and-workflow
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-btp-user-role-request
JSON
/artifacts/miyasuta-btp-user-role-request.json
MCP
Connecting an agent