ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aditya Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9516) User should be notified with success message on Creating New Routing
Date Wed, 09 Aug 2017 04:35:01 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119400#comment-16119400

Aditya Sharma commented on OFBIZ-9516:

Currently, we use a success message for Production Run as:
{quote}ProductionRun ${productionRunId} created{quote}

IMO workEffort has been underlying data model for a variety of applications like routing,
task etc so it would futile showing "Work Effort" keyword in the message.
A user is not aware of underlying data model & even it doesn't matter to a user where
the data is being stored.
I prefer we use workEffortType here to make the message more user-friendly.

I would suggest message to be 

{quote}${workEffortType}: ${workEffortId} created successfully{quote}

> User should be notified with success message on Creating New Routing
> --------------------------------------------------------------------
>                 Key: OFBIZ-9516
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9516
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: manufacturing
>    Affects Versions: Trunk
>            Reporter: Aditya Sharma
>            Assignee: Aditya Sharma
>            Priority: Trivial
>         Attachments: OFBIZ-9516.patch
> Steps to regenerate:
> 1. Go to Manufacturing component (https://localhost:8443/manufacturing/control/main)
> 2. Click on Routing sub menu (https://localhost:8443/manufacturing/control/FindRouting)
> 3. Click on New Routing button.(https://localhost:8443/manufacturing/control/EditRouting)
> 4. Fill required fields and Click Submit button.
> 7. On success, the user should be notified with success message.

This message was sent by Atlassian JIRA

View raw message