8000 [RSR-384] COMPAS - EVOL - The service which creates new SCD file can accept a Header Id as input · Issue #71 · com-pas/compas-sct · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[RSR-384] COMPAS - EVOL - The service which creates new SCD file can accept a Header Id as input #71
Closed
@jeanetiennelemaire

Description

@jeanetiennelemaire

As a COMPAS service user, this US purpose is to update an already existing COMPAS service RSR-31 that generate a new SCD file. Currently, this service generates by itself the Header ID of the new SCD file. Now, this service shall accept the Header ID of the new SCD file as input.

 

As service user, I would like to update the service which creates a new SCD file. This SCD file has a Header ID which is either:

generated automatically if it is not provided as input
provided as input. In this case the service checks that Header ID, Header Version and Header Revision provided as input, does not already exist
  

Prerequisites: 

The following COMPAS services have already been developed:
RSR-31   to create a new SCD file
 

The inputs of this service are:

For the new SCD to create
Header.Id (string) (optional)
And Header.Version and Header.Revision (string) (required)
And Hitem.Who, Hitem.What, Hitem.Why (string) (optional)
 

US process description:

The Header ID of the new SCD file to create is optional:
if it is not provided as input then the service generates it automatically
if it is provided as input then the service uses it to creates SCD file 
 

Output:

The Header.id, Header.revision, Header.version are output
 

Error messages:

If a required input is missing then the processing is aborted and an error message is returned: "The input_name is required. End of the processing."

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0