The flowfilloutclientppg from stephanybatista

Create list sharepoint "Inscription Type"

The name of list must be "Tipo Inscricao"

Create list sharepoint "Payment Condition"

Must create list of type item in sharepoint

Add event to save flow Customer

When user calls the event "Salvar fluxo Customer", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.

Now, the request must be with status "Started"

N° 7 - The datas are filled in Customer form, but aren't saved

Send e-mail in every flow

Must send e-mail in every flow with the fields of request.

Create lista sharepoint "Contributor Type"

The name of list must be "Tipo Contribuinte"

Phone type 2 is duplicate in screen

N° 5 - Open link in new tab to don't have broken layout

If approval status is approved, observation is not required

Insert link to user view the full request in Sharepoint

Validate if flow released is allowed to user

Create list sharepoint "Sub-Branch Activity"

Must create list of type item in sharepoint

Add flow Cadastre

In the flow must exist only the fields of approval.

Change Request UI to add Customer flow fields

The Request UI must be to changed to add Customer flow fields (https://onedrive.live.com/edit.aspx?cid=C32EDCA9C6DEA816&resid=c32edca9c6dea816!18660&app=Excel). Moreover, must be added the fields: status of approval and observation of approval.

When user calls the event "Salvar fluxo Customer", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.

N° 6 - When edit the field "Volume - Data Vigencia" occurs a post back and back to tab of request.

N° 9 - Check labels of client impression screen that are wrong

Change request UI to add all flows

Create list sharepoint "Client Request"

The fields for creation are:

Create list sharepoint "SaleOrder"

The name of list must be "Ordem Venda"

N° 2 - Mask of field "CNPJ/CPF" allow only CNPJ

N° 4 - Form edition of evaluation is not intuitive

Create project and to send for git

N° 11 - Link in e-mail of return is wrong, points out to supplier flow

Create object model by lists sharepoint

Create workflow to request client

Must create workflow to get inputs of screen and to save in list.

Add event to save flow CAS

When user calls the event "Salvar fluxo CAS", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.
Status returned: Validate if the field observation of approval was filled. After, the system must return o flow to group Customer

Load current task status to approval

N° 3 - E-mail don't sent when request is saved

Create list sharepoint "Phone Type"

Must create the list of type item in sharepoint

Create list sharepoint "Purchases Group"

Must create list of type item in sharepoint

N° 1 - Layout broken

Create list sharepoint " PBC Group"

Must create list of type item in sharepoint

Create flow customer

The flow must be created a task after of request and all people of this group (customer) must receive e-mail about the request

Create list sharepoint "Branch Activity"

Must create list of type item in sharepoint

Create list sharepoint "UserOfClientRegistration"

The name of list must be "Usuário Cadastro Cliente" and must be a field to group (Customer, Fiscal, CAS, Logistica, Crédito)

Create list sharepoint "TaskClientRegistration"

The list name must be "Tarefa cadastro cliente"

Create screen to request client

Must create screen with the fields of lists to request client.

Add event to save flow Fiscal

When user calls the event "Salvar fluxo Fiscal", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.
Status returned: Validate if the field observation of approval was filled. After, the system must return o flow to group Customer

Mask in field Data

Create list sharepoint "Payment Method"

The name of list must be "Metodo Pagamento"

Create list sharepoint "Client Group"

Must create list of type item in sharepoint

Create Task UI

The task UI must select all the tasks of user group and show in grid.

Create event to validate and to save client request in list

Must get the fields of UI and to save in list

Add event to save flow Credit

When user calls the event "Salvar fluxo Credit", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.
Status returned: Validate if the field observation of approval was filled. After, the system must return o flow to group Customer

Add event to save flow Logistics

When user calls the event "Salvar fluxo Logistics", the system must validate the items below:

Status approved: Validate if all the fields of flow were filled. After, the system must pass to next flow.
Status disapproved: Validate if the field observation of approval was filled. After, the system must finalize the request.
Status returned: Validate if the field observation of approval was filled. After, the system must return o flow to group Customer

stephanybatista / flowfilloutclientppg Goto Github PK

flowfilloutclientppg's People

Contributors

Watchers

flowfilloutclientppg's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs