Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

User Story 1: Find Invoice

The user should be able to search invoices (Sales, Purchase etc..) in the system and be able to filter records based on invoice Id, status, invoice date, invoice description etc.. A link to the invoice should be provided w.r.t. each invoice coming in the result set, to navigate the user to a quick view of respective invoice.

 

Use Case Name

Find Invoice

ActorAccount Manager
DescriptionUser should be able to search invoices (Sales, Purchase etc..) in the system.

Trigger

The Account Manager accesses the accounting.

Precondition

None.

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on [Invoices] tab.

  3. The system displays a search form to find invoice.

  4. User clicks on [Find] button.

  5. The system successfully finds all invoices.

  6. Now User can filter records based on invoice id, status, invoice date, invoice description etc...

  7. The system successfully displays records based on a filter.

Post-condition

User is able to Find Invoices.

  
User Story 2: View Invoice

The user can navigate to an invoice detail view from search result set. The user should be able to review invoice for its Order, Customer / Vendor, Date, Due Date, Payment Applied, Items. The user should be able to generate PDF from invoice detail view for the corresponding invoice.

Use Case Name

View Invoice

ActorAccount Manager
DescriptionUser should be able to search invoices (Sales, Purchase etc..) in the system.

Trigger

The Account Manager accesses the accounting.

Precondition

None.

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on [Invoices] tab.

  3. The system displays a search form to find invoice.

  4. User clicks on [Find] button.

  5. The system successfully finds all invoices.

  6. Click on the 'Invoice Id' link in the result set.

  7. Now user can view the invoice details

Post-condition

User is able to view invoice details

  
User Story 3: Update Invoice Status

 

Use Case Name

Update Invoice Status

Actor

Account Manager

Description

User should be able to update the invoice status of the system.

Trigger

The Account Manager accesses the accounting.

Precondition

 None

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on [Invoices] tab.

  3. The system displays a search form to find Invoices.

  4. User clicks on [Find] button.

  5. Click on the 'Invoice Id' link in the result set.

  6. The user can update invoice status on the basis of current status respectively.

Post-condition

User is able to update invoice status

 

User Story 4: Create Payment

Use Case Name

Create Payment

Actor

Account Manager

Description

User should be able to create a new payment

Trigger

The Account Manager accesses the accounting.

Precondition

 None

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on the [Payments] tab.

  3. User clicks on the [Create new payment] tab.

  4. The user can create an incoming or outgoing payment.

  5. The user needs to feed required fields.

  6. User clicks on [Create] button.

  7. Payment created successfully.

Post-condition

User is able to create a new payment.
User Story 5: Find Payment

Use Case Name

FInd Payment

Actor

Account Manager

Description

User should be able to Find Payment in the system.

Trigger

 

Precondition

NONE

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on the [Payments] tab.

  3. The system displays a search form to find Payment.

  4. User clicks on [Find] button.

  5. The system successfully finds all Payments.

  6. Now User can filter records based on payment id, payment type, status, From party id, To party Id etc...

  7. System successfully displays records based on filter

Post-condition

User is able to Find Payments.

User Story 6: View Payment

Use Case Name

View Payment

Actor

Account Manager

Description

  1. User should be able to view payment in the system

Trigger

The Account Manager accesses the accounting.

Precondition

 None

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on the [Payments] tab.

  3. The system displays a search form to find Payment.

  4. User clicks on [Find] button.

  5. The system successfully finds all Payments.

  6. User clicks on payment id.

  7. The system successfully views payments.

Post-condition

User is able to view payment status.
User Story 7: Edit Payment

Use Case Name

Edit Payment

Actor

Account Manager

Description

  1. User should be able to edit the payment

Trigger

The Account Manager accesses the accounting.

Precondition

 None

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on the [Payments] tab.

  3. The system displays a search form to find Payment.

  4. User clicks on [Find] button.

  5. The system successfully finds all Payments.

  6. User clicks on payment id.

  7. The system successfully views payment.

  8. User clicks on the [Update] tab of payment header section.

  9. User edits the payment details.

  10. User clicks on  [Submit].

  11. User successfully updates the payment details.

Post-condition

User is able to update payment details.
User Story 8: Update Payment Status

The system should allow the user to update the status manually to 'Received' or 'Cancel'. 

Use Case Name

Update Payment Status

Actor

Account Manager

Description

  1. User Should be able to update the payment status. 

Trigger

The Account Manager accesses the accounting.

Precondition

 None

Basic Path

  1. User selects 'Accounting' menu item.

  2. User clicks on the [Payments] tab.

  3. The system displays a search form to find Payment.

  4. User clicks on [Find] button.

  5. The system successfully finds all Payments.

  6. User clicks on payment id.

  7. The system successfully views payment.
  8. The user can update the Payment status on the basis of current status.

Post-condition

User is able to update payment status.
  • No labels