You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
For now the billing page looks like this:
It may look confusing for billing persons because of the following issues:
There is no name of the product, which is the human-like representation of the product (like domains instead of ip-addresses). It is easier to make a mistake if you have only numbers where you could have names.
To look which product is represented by a row, the billing person would need to copy the licencePlate, leave the Billing Page for the Products page and paste the licencePlate to the search field.
The page show 3 persons but status only for interaction with two persons (Expense Authority and Billing Reviewer).
Current tags are showing the backend status instead of global status of the Request:
when the request is signed by Expense Authority person, it receives the tag Signed
when the request is signed by Billing Reviewer (Cloud Director), it receives the tag Approved (which may be confusing, because in global sense it is still waiting for the Approval by Admin. If we map this status to the global status it will be Signed by Expense Authority and Billing Reviewer but not Approved. And as the billing persons are not aware of backend stuff, they may be confused. Actually renaming the Approved tag to Reviewed tag would make much more sense.
Below is the schema of current matching of the status of the Billing Page to the Global Request status as well as proposal of changes:
Here is an example of how we show the status of the Request at Requests tab. Maybe we could foster similar layout for the stages of the Requests as on the picture below. The columns would be named as the roles: Expense Authority, Billing Reviewer, Admin Approver(or something similar). And while going through the different stages, the round icon of the person would change to the checkbox icon (as on the picture below). And while it is not through this stage, the person Icon and name would be greyed out.
The text was updated successfully, but these errors were encountered:
Description:
For now the billing page looks like this:
It may look confusing for
billing persons
because of the following issues:billing person
would need to copy thelicencePlate
, leave theBilling Page
for theProducts page
and paste thelicencePlate
to thesearch field
.Expense Authority
andBilling Reviewer
).backend status
instead ofglobal status
of theRequest
:Expense Authority
person, it receives the tagSigned
Billing Reviewer
(Cloud Director
), it receives the tagApproved
(which may be confusing, because in global sense it is still waiting for theApproval
byAdmin
. If we map this status to the global status it will beSigned by Expense Authority and Billing Reviewer
butnot Approved
. And as thebilling persons
are not aware of backend stuff, they may be confused. Actually renaming theApproved
tag toReviewed
tag would make much more sense.Below is the schema of current matching of the status of the Billing Page to the Global Request status as well as proposal of changes:
Here is an example of how we show the status of the
Request
atRequests tab
. Maybe we could foster similar layout for the stages of theRequests
as on the picture below. The columns would be named as the roles:Expense Authority
,Billing Reviewer
,Admin Approver
(or something similar). And while going through the different stages, the round icon of the person would change to the checkbox icon (as on the picture below). And while it is not through this stage, the person Icon and name would be greyed out.The text was updated successfully, but these errors were encountered: