[jira] [Commented] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624645#comment-16624645 ] Sonal Patwari commented on OFBIZ-9597: -- Done following in [CRM Process Overview|https://cwiki.apache.org/confluence/x/RpJjB]: 1. Verified the process of lead management and added some important key fields in the lead management process. 2. Tried running the process of Event management in ofbiz but not able to create the event. So, created a ticket OFBIZ-10583 for the same. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari >Priority: Major > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10583) Issue while creating any new event
[ https://issues.apache.org/jira/browse/OFBIZ-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10583: -- Description: Steps to regenerate: # Navigate to [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. # Try to create a new event. # On clicking Add button an error occurs. # Attached the screenshot of the error was: Steps to regenerate: # Navigate to [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events[]|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. # Try to create a new event. # On clicking Add button an error occurs. # Attached the screenshot of the error > Issue while creating any new event > -- > > Key: OFBIZ-10583 > URL: https://issues.apache.org/jira/browse/OFBIZ-10583 > Project: OFBiz > Issue Type: Bug >Affects Versions: 17.12.01 >Reporter: Sonal Patwari >Priority: Major > Attachments: CreateEventIssue.jpg > > > Steps to regenerate: > # Navigate to > [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. > # Try to create a new event. > # On clicking Add button an error occurs. > # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10583) Issue while creating any new event
Sonal Patwari created OFBIZ-10583: - Summary: Issue while creating any new event Key: OFBIZ-10583 URL: https://issues.apache.org/jira/browse/OFBIZ-10583 Project: OFBiz Issue Type: Bug Affects Versions: 17.12.01 Reporter: Sonal Patwari Attachments: CreateEventIssue.jpg Steps to regenerate: # Navigate to [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events[]|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. # Try to create a new event. # On clicking Add button an error occurs. # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9969) In 'ValidateMethod.java', when we don't pass any className from xml files. default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for className.
[ https://issues.apache.org/jira/browse/OFBIZ-9969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9969: - Attachment: OFBIZ-9969.patch I have attached the updated patch. > In 'ValidateMethod.java', when we don't pass any className from xml files. > default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for > className. > --- > > Key: OFBIZ-9969 > URL: https://issues.apache.org/jira/browse/OFBIZ-9969 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Deepak Dixit > Fix For: Upcoming Release > > Attachments: OFBIZ-9969.patch, OFBIZ-9969.patch > > > *Actual:* In 'ValidateMethod.java', If we have not passed any className from > the xml files.Then, className is set to null and throws an error of > 'Validation Method not found'. > *Expected:* A default value 'org.apache.ofbiz.base.util.UtilValidate' should > be assigned to the className. > As reference: Visit 'ValidateMethodCondition.java' and there, 'className' is > set with a default value 'org.apache.ofbiz.base.util.UtilValidate'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302426#comment-16302426 ] Sonal Patwari commented on OFBIZ-9597: -- Done following in [CRM Process Review|https://cwiki.apache.org/confluence/x/RpJjB]: 1. Created Level-3 diagram for Sales Forecast process. 2. Added Opportunities section and some information related to it. 3. Created Level-1 diagram for Opportunities. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302426#comment-16302426 ] Sonal Patwari edited comment on OFBIZ-9597 at 12/23/17 1:10 PM: Done following in [CRM Process Overview|https://cwiki.apache.org/confluence/x/RpJjB]: 1. Created Level-3 diagram for Sales Forecast process. 2. Added Opportunities section and some information related to it. 3. Created Level-1 diagram for Opportunities. was (Author: sonal.patwari): Done following in [CRM Process Review|https://cwiki.apache.org/confluence/x/RpJjB]: 1. Created Level-3 diagram for Sales Forecast process. 2. Added Opportunities section and some information related to it. 3. Created Level-1 diagram for Opportunities. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10012: -- Description: Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. 6. For reference screenshot is attached. was: Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10012: -- Attachment: ContentSearchOptionsAlertShowing (1).png > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
Sonal Patwari created OFBIZ-10012: - Summary: Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup Key: OFBIZ-10012 URL: https://issues.apache.org/jira/browse/OFBIZ-10012 Project: OFBiz Issue Type: Bug Components: content Affects Versions: Trunk Reporter: Sonal Patwari Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10007) Party Classification Groups are not listing on FindParty screen.
Sonal Patwari created OFBIZ-10007: - Summary: Party Classification Groups are not listing on FindParty screen. Key: OFBIZ-10007 URL: https://issues.apache.org/jira/browse/OFBIZ-10007 Project: OFBiz Issue Type: Bug Components: party Reporter: Sonal Patwari - Navigate to [Find Party|https://demo-trunk.ofbiz.apache.org/partymgr/control/findparty] Screen. - Check Classification group dropdown > List is empty.. - Refer attached screenshot for more clarity of the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10007) Party Classification Groups are not listing on FindParty screen.
[ https://issues.apache.org/jira/browse/OFBIZ-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10007: -- Attachment: FindPartyPageClassificationGroupsNotListing.png > Party Classification Groups are not listing on FindParty screen. > > > Key: OFBIZ-10007 > URL: https://issues.apache.org/jira/browse/OFBIZ-10007 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Sonal Patwari > Attachments: FindPartyPageClassificationGroupsNotListing.png > > > - Navigate to [Find > Party|https://demo-trunk.ofbiz.apache.org/partymgr/control/findparty] Screen. > - Check Classification group dropdown > List is empty.. > - Refer attached screenshot for more clarity of the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9999) Remove unused service checkContentAssocIds and its usage
[ https://issues.apache.org/jira/browse/OFBIZ-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-: - Attachment: OFBIZ-.patch Removed unused service 'checkContentAssocIds' and its usage and provided the patch in the attachment. > Remove unused service checkContentAssocIds and its usage > > > Key: OFBIZ- > URL: https://issues.apache.org/jira/browse/OFBIZ- > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Suraj Khurana >Assignee: Sonal Patwari > Attachments: OFBIZ-.patch > > > Earlier it was used to check parameters related to ContentAssoc record, but > now createContentAssoc service itself is entity-auto service and so we don't > need this service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9999) Remove unused service checkContentAssocIds and its usage
[ https://issues.apache.org/jira/browse/OFBIZ-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-: Assignee: Sonal Patwari (was: Suraj Khurana) > Remove unused service checkContentAssocIds and its usage > > > Key: OFBIZ- > URL: https://issues.apache.org/jira/browse/OFBIZ- > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Suraj Khurana >Assignee: Sonal Patwari > > Earlier it was used to check parameters related to ContentAssoc record, but > now createContentAssoc service itself is entity-auto service and so we don't > need this service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9968: - Attachment: OFBIZ-9968.patch Removed hard coded dollar icons from uiLabels. I have verified the changes on the local instance. Please find the attached patch. Thanks! > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > Attachments: OFBIZ-9968.patch > > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. Hardcoded dollar icons bound the user. If there is an Indian > business, So currency-uom-id will be INR instead of US Dollar. So, to make it > consistent. Hardcoded dollar icons should be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9969) In 'ValidateMethod.java', when we don't pass any className from xml files. default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for className.
[
https://issues.apache.org/jira/browse/OFBIZ-9969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sonal Patwari updated OFBIZ-9969:
-
Attachment: OFBIZ-9969.patch
In 'ValidateMethod.java', set 'className' with
{code:java}
'MiniLangValidate.checkAttribute(element.getAttribute("class"),
"org.apache.ofbiz.base.util.UtilValidate")
{code}
instead of
{code:java}
'element.getAttribute("class")
{code}
In the previous code, If we do not pass any className from the xml files.Then,
className is set to null and throws an error of 'Validation Method not found'.
I have verified the changes on the local instance. Please find the attached
patch. Thanks!
> In 'ValidateMethod.java', when we don't pass any className from xml files.
> default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for
> className.
> ---
>
> Key: OFBIZ-9969
> URL: https://issues.apache.org/jira/browse/OFBIZ-9969
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Sonal Patwari
>Assignee: Sonal Patwari
> Attachments: OFBIZ-9969.patch
>
>
> *Actual:* In 'ValidateMethod.java', If we have not passed any className from
> the xml files.Then, className is set to null and throws an error of
> 'Validation Method not found'.
> *Expected:* A default value 'org.apache.ofbiz.base.util.UtilValidate' should
> be assigned to the className.
> As reference: Visit 'ValidateMethodCondition.java' and there, 'className' is
> set with a default value 'org.apache.ofbiz.base.util.UtilValidate'.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9967) In 'updateOrderContactMech' service, A check should be added to call 'removeOrderContactMech'.
[ https://issues.apache.org/jira/browse/OFBIZ-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9967: - Attachment: OFBIZ-9967.patch Added a 'if-not-empty' check for 'oldContactMechId' field i.e, if 'oldContactMechId' is available then only 'removeOrderContactMech' service should be called in 'updateOrderContactMech' service. I have verified the changes on the local instance. Please find the attached patch. Thanks! > In 'updateOrderContactMech' service, A check should be added to call > 'removeOrderContactMech'. > -- > > Key: OFBIZ-9967 > URL: https://issues.apache.org/jira/browse/OFBIZ-9967 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > Attachments: OFBIZ-9967.patch > > > In case, user don't create orderContactMech while creating an order and wish > to create orderContactMech after the creation then, 'updateOrderContactMech' > throws error of 'oldContactMechId' parameter missing in > 'removeOrderContactMech' service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9969) In 'ValidateMethod.java', when we don't pass any className from xml files. default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for className.
Sonal Patwari created OFBIZ-9969: Summary: In 'ValidateMethod.java', when we don't pass any className from xml files. default value 'org.apache.ofbiz.base.util.UtilValidate' should be set for className. Key: OFBIZ-9969 URL: https://issues.apache.org/jira/browse/OFBIZ-9969 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Sonal Patwari Assignee: Sonal Patwari *Actual:* In 'ValidateMethod.java', If we have not passed any className from the xml files.Then, className is set to null and throws an error of 'Validation Method not found'. *Expected:* A default value 'org.apache.ofbiz.base.util.UtilValidate' should be assigned to the className. As reference: Visit 'ValidateMethodCondition.java' and there, 'className' is set with a default value 'org.apache.ofbiz.base.util.UtilValidate'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240157#comment-16240157 ] Sonal Patwari commented on OFBIZ-9968: -- Hello Jacques and Deepak, Thanks for your suggestion. Now, I have added the description. > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. Hardcoded dollar icons bound the user. If there is an Indian > business, So currency-uom-id will be INR instead of US Dollar. So, to make it > consistent. Hardcoded dollar icons should be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9968: - Description: For example: In 'ProductPromoUiLabels.xml' file 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded dollar icons. Hardcoded dollar icons bound the user. If there is an Indian business, So currency-uom-id will be INR instead of US Dollar. So, to make it consistent. Hardcoded dollar icons should be removed. (was: For example: In 'ProductPromoUiLabels.xml' file 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded dollar icons.) > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. Hardcoded dollar icons bound the user. If there is an Indian > business, So currency-uom-id will be INR instead of US Dollar. So, to make it > consistent. Hardcoded dollar icons should be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9967) In 'updateOrderContactMech' service, A check should be added to call 'removeOrderContactMech'.
[ https://issues.apache.org/jira/browse/OFBIZ-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-9967: Assignee: Sonal Patwari > In 'updateOrderContactMech' service, A check should be added to call > 'removeOrderContactMech'. > -- > > Key: OFBIZ-9967 > URL: https://issues.apache.org/jira/browse/OFBIZ-9967 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > > In case, user don't create orderContactMech while creating an order and wish > to create orderContactMech after the creation then, 'updateOrderContactMech' > throws error of 'oldContactMechId' parameter missing in > 'removeOrderContactMech' service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-9968: Assignee: Sonal Patwari > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Sonal Patwari > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9968: - Description: For example: In 'ProductPromoUiLabels.xml' file 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded dollar icons. (was: For example: In 'ProductPromoUiLabels.xml' file 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded dollar icons. So, ) > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9968: - Description: For example: In 'ProductPromoUiLabels.xml' file 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded dollar icons. So, (was: For example: In '/product/config/ProductPromoUiLabels.xml' file ) > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari > > For example: In 'ProductPromoUiLabels.xml' file > 'ProductPromoCondition.PPIP_PRODUCT_TOTAL', > 'ProductPromoCondition.PPIP_PRODUCT_AMOUNT' etc. uilabels contain hardcoded > dollar icons. So, -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
[ https://issues.apache.org/jira/browse/OFBIZ-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9968: - Description: For example: In '/product/config/ProductPromoUiLabels.xml' file > Hardcoded dollar icons should be removed from uiLabels. > --- > > Key: OFBIZ-9968 > URL: https://issues.apache.org/jira/browse/OFBIZ-9968 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari > > For example: In '/product/config/ProductPromoUiLabels.xml' file -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9967) In 'updateOrderContactMech' service, A check should be added to call 'removeOrderContactMech'.
Sonal Patwari created OFBIZ-9967: Summary: In 'updateOrderContactMech' service, A check should be added to call 'removeOrderContactMech'. Key: OFBIZ-9967 URL: https://issues.apache.org/jira/browse/OFBIZ-9967 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Sonal Patwari In case, user don't create orderContactMech while creating an order and wish to create orderContactMech after the creation then, 'updateOrderContactMech' throws error of 'oldContactMechId' parameter missing in 'removeOrderContactMech' service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9968) Hardcoded dollar icons should be removed from uiLabels.
Sonal Patwari created OFBIZ-9968: Summary: Hardcoded dollar icons should be removed from uiLabels. Key: OFBIZ-9968 URL: https://issues.apache.org/jira/browse/OFBIZ-9968 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Sonal Patwari -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9896) Incorrect success message after creating prospect
Sonal Patwari created OFBIZ-9896: Summary: Incorrect success message after creating prospect Key: OFBIZ-9896 URL: https://issues.apache.org/jira/browse/OFBIZ-9896 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Sonal Patwari Navigate to [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], after creating the prospect, success message 'ProductStoreRole is created successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9894) Dropdown dependent mechanism should be there while selecting any Sales Forecast detail
Sonal Patwari created OFBIZ-9894: Summary: Dropdown dependent mechanism should be there while selecting any Sales Forecast detail Key: OFBIZ-9894 URL: https://issues.apache.org/jira/browse/OFBIZ-9894 Project: OFBiz Issue Type: Bug Reporter: Sonal Patwari Navigate to SFA component and on Sales Forecast screen, after creating a forecast when we add forecast details, it allows us to add any of the fields separately without depending on the other fields. Expected result: There should be a dependency while selecting forecast details. For example, While adding quantity, quantity UOM field should be dependent and vice versa should also be possible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9753) 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on FindSalesOpportunity screen.
[ https://issues.apache.org/jira/browse/OFBIZ-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9753: - Description: Navigate to SFA component > Opportunities > FindSalesOpportunity. On opportunity search field 'Find Opportunities' is reflecting instead of 'Opportunity Id' Here is the links for reference: [Find Sales Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] Below is the image attached for reference. was: Navigate to SFA component > Opportunities > FindSalesOpportunity. On opportunity search field 'Find Opportunities' is reflecting instead of 'Opportunity Id' Here is the links for reference: [Find Sales Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] Be > 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on > FindSalesOpportunity screen. > -- > > Key: OFBIZ-9753 > URL: https://issues.apache.org/jira/browse/OFBIZ-9753 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 16.11 >Reporter: Sonal Patwari > Attachments: SFA Manager_Find Opportunities.png > > > Navigate to SFA component > Opportunities > FindSalesOpportunity. > On opportunity search field 'Find Opportunities' is reflecting instead of > 'Opportunity Id' > Here is the links for reference: > [Find Sales > Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] > Below is the image attached for reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9753) 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on FindSalesOpportunity screen.
[ https://issues.apache.org/jira/browse/OFBIZ-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9753: - Attachment: SFA Manager_Find Opportunities.png > 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on > FindSalesOpportunity screen. > -- > > Key: OFBIZ-9753 > URL: https://issues.apache.org/jira/browse/OFBIZ-9753 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 16.11 >Reporter: Sonal Patwari > Attachments: SFA Manager_Find Opportunities.png > > > Navigate to SFA component > Opportunities > FindSalesOpportunity. > On opportunity search field 'Find Opportunities' is reflecting instead of > 'Opportunity Id' > Here is the links for reference: > [Find Sales > Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9753) 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on FindSalesOpportunity screen.
[ https://issues.apache.org/jira/browse/OFBIZ-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9753: - Description: Navigate to SFA component > Opportunities > FindSalesOpportunity. On opportunity search field 'Find Opportunities' is reflecting instead of 'Opportunity Id' Here is the links for reference: [Find Sales Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] Be was: Navigate to SFA component > Opportunities > FindSalesOpportunity. On opportunity search field 'Find Opportunities' is reflecting instead of 'Opportunity Id' Here is the links for reference: [Find Sales Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] > 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on > FindSalesOpportunity screen. > -- > > Key: OFBIZ-9753 > URL: https://issues.apache.org/jira/browse/OFBIZ-9753 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 16.11 >Reporter: Sonal Patwari > Attachments: SFA Manager_Find Opportunities.png > > > Navigate to SFA component > Opportunities > FindSalesOpportunity. > On opportunity search field 'Find Opportunities' is reflecting instead of > 'Opportunity Id' > Here is the links for reference: > [Find Sales > Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] > Be -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9753) 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on FindSalesOpportunity screen.
Sonal Patwari created OFBIZ-9753: Summary: 'Find Opportunities' field name is reflecting in place of 'Opportunity Id' on FindSalesOpportunity screen. Key: OFBIZ-9753 URL: https://issues.apache.org/jira/browse/OFBIZ-9753 Project: OFBiz Issue Type: Bug Affects Versions: Release Branch 16.11 Reporter: Sonal Patwari Navigate to SFA component > Opportunities > FindSalesOpportunity. On opportunity search field 'Find Opportunities' is reflecting instead of 'Opportunity Id' Here is the links for reference: [Find Sales Opportunity|https://demo-stable.ofbiz.apache.org/sfa/control/FindSalesOpportunity] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9680) No option to add Event Purpose on Events page.
Sonal Patwari created OFBIZ-9680: Summary: No option to add Event Purpose on Events page. Key: OFBIZ-9680 URL: https://issues.apache.org/jira/browse/OFBIZ-9680 Project: OFBiz Issue Type: Bug Reporter: Sonal Patwari Navigate to SFA component > Events > Create Event. - While creating an event, there is no option to enter purpose. - On Events screen there is 'Purpose' field in the table which remains empty as there is no option for adding it. Here are the helpful links : - [Events Page|https://demo-stable.ofbiz.apache.org/sfa/control/Events] - [Create Event|https://demo-stable.ofbiz.apache.org/sfa/control/EditEvent] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147259#comment-16147259 ] Sonal Patwari commented on OFBIZ-9597: -- Added event management process diagrams in [CRM Process Overview|https://cwiki.apache.org/confluence/x/RpJjB] document. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142805#comment-16142805 ] Sonal Patwari commented on OFBIZ-9597: -- I have added some activity diagrams of customer management and lead management process in [CRM Process Overview|https://cwiki.apache.org/confluence/x/RpJjB]. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9651) Page is not redirected properly after adding 'Lead Source' on 'View Lead' page.
Sonal Patwari created OFBIZ-9651: Summary: Page is not redirected properly after adding 'Lead Source' on 'View Lead' page. Key: OFBIZ-9651 URL: https://issues.apache.org/jira/browse/OFBIZ-9651 Project: OFBiz Issue Type: Bug Affects Versions: Release Branch 16.11 Reporter: Sonal Patwari Priority: Minor Navigate to SFA component > Leads > select any lead > add lead source. Here is the link: [https://demo-stable.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD&partyId=sfa101] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138351#comment-16138351 ] Sonal Patwari commented on OFBIZ-9597: -- Here is the document link [CRM Process Overview|https://cwiki.apache.org/confluence/x/RpJjB] which I have created and added process overview in the document. > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9615) Documentation: Manufacturing User Stories, Use Cases and Test Cases
Sonal Patwari created OFBIZ-9615: Summary: Documentation: Manufacturing User Stories, Use Cases and Test Cases Key: OFBIZ-9615 URL: https://issues.apache.org/jira/browse/OFBIZ-9615 Project: OFBiz Issue Type: Sub-task Reporter: Sonal Patwari Manufacturing business process user stories, use cases and test cases to be documented. *Doc Content*: Every Manufacturing business activity to be covered under below-given headings- - User Story (Write, if doesn't exist already OR review and refine as required) - Use Cases (Write, if don't exist already OR review and refine as required) - Test Cases (Write, if don't exist already OR review and refine as required. Verify every test case and mark it with appropriate status- PASS, FAIL). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9613) Documentation: Manufacturing Process Overview
Sonal Patwari created OFBIZ-9613: Summary: Documentation: Manufacturing Process Overview Key: OFBIZ-9613 URL: https://issues.apache.org/jira/browse/OFBIZ-9613 Project: OFBiz Issue Type: Sub-task Reporter: Sonal Patwari Manufacturing process overview to be documented. *Doc Content*: Every Sales Order Management business activity to be covered with below-given headings- - Process Overview - Business Purpose (significance of having efficient manufacturing capabilities in real world) - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9609) Documentation: Order Fulfillment Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9609: - Description: Order Fulfillment process overview to be documented. *Doc Content*: Every Order fulfillment business activity to be covered with below-given headings- - Process Overview - Business Purpose (significance of having efficient Order fulfillment capabilities in real world) - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the process flow) was: Order Fulfillment process overview to be documented. *Doc Content*: Every Order fulfillment business activity to be covered with below-given headings- - Process Overview - Business Purpose (significance of having efficient Order fulfillment capabilities in real world) - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the process flow) > Documentation: Order Fulfillment Process Overview > - > > Key: OFBIZ-9609 > URL: https://issues.apache.org/jira/browse/OFBIZ-9609 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sonal Patwari > Labels: BPRB, Fulfillment, OBPRB, Order > > Order Fulfillment process overview to be documented. > *Doc Content*: > Every Order fulfillment business activity to be covered with below-given > headings- > - Process Overview > - Business Purpose (significance of having efficient Order fulfillment > capabilities in real world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9612) Documentation: Order Fulfillment User Stories, Use Cases and Test Cases
Sonal Patwari created OFBIZ-9612: Summary: Documentation: Order Fulfillment User Stories, Use Cases and Test Cases Key: OFBIZ-9612 URL: https://issues.apache.org/jira/browse/OFBIZ-9612 Project: OFBiz Issue Type: Sub-task Reporter: Sonal Patwari Order Fulfillment business process user stories, use cases and test cases to be documented. *Doc Content*: Every Order Fulfillment business activity to be covered under below-given headings- - User Story (Write, if doesn't exist already OR review and refine as required) - Use Cases (Write, if don't exist already OR review and refine as required) - Test Cases (Write, if don't exist already OR review and refine as required. Verify every test case and mark it with appropriate status- PASS, FAIL). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9609) Documentation: Order Fulfillment Process Overview
Sonal Patwari created OFBIZ-9609: Summary: Documentation: Order Fulfillment Process Overview Key: OFBIZ-9609 URL: https://issues.apache.org/jira/browse/OFBIZ-9609 Project: OFBiz Issue Type: Sub-task Reporter: Sonal Patwari Order Fulfillment process overview to be documented. *Doc Content*: Every Order fulfillment business activity to be covered with below-given headings- - Process Overview - Business Purpose (significance of having efficient Order fulfillment capabilities in real world) - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9598) Documentation: Customer Relationship Management (CRM) User Stories, Use Cases and Test Cases
[ https://issues.apache.org/jira/browse/OFBIZ-9598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-9598: Assignee: Sonal Patwari > Documentation: Customer Relationship Management (CRM) User Stories, Use Cases > and Test Cases > - > > Key: OFBIZ-9598 > URL: https://issues.apache.org/jira/browse/OFBIZ-9598 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM business process user stories, use cases and test cases to be documented. > *Doc Content:* > Every CRM business activity to be covered under below-given headings- > - User Story (Write, if doesn't exist already OR review and refine as > required) > - Use Cases (Write, if don't exist already OR review and refine as required) > - Test Cases (Write, if don't exist already OR review and refine as required. > Verify every test case and mark it with appropriate status- PASS, FAIL). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-9597: Assignee: Sonal Patwari > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Sonal Patwari > Labels: BPRB, CRM, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9516) User should be notified with success message on Creating New Routing
[
https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119408#comment-16119408
]
Sonal Patwari edited comment on OFBIZ-9516 at 8/9/17 7:31 AM:
--
Thanks Pranay, Pierre and Aditya for your comments.
I agree with Aditya as
{code:java}
'${workEffortType}: ${workEffortId} created successfully'
{code}
would be more generic and convenient.
was (Author: sonal.patwari):
Thanks Pranay, Pierre and Aditya for your comments.
I agree with Aditya as '${workEffortType}: ${workEffortId} created
successfully' would be more generic and convenient.
> 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
(v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9516) User should be notified with success message on Creating New Routing
[
https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119408#comment-16119408
]
Sonal Patwari edited comment on OFBIZ-9516 at 8/9/17 4:49 AM:
--
Thanks Pranay, Pierre and Aditya for your comments.
I agree with Aditya as '${workEffortType}: ${workEffortId} created
successfully' would be more generic and convenient.
was (Author: sonal.patwari):
Thanks Pranay, Pierre and Aditya for your comments.
I agree with Aditya as '${workEffortType}: ${workEffortId} created
successfully' would be more generic and convenient.
> 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
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9516) User should be notified with success message on Creating New Routing
[
https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119408#comment-16119408
]
Sonal Patwari commented on OFBIZ-9516:
--
Thanks Pranay, Pierre and Aditya for your comments.
I agree with Aditya as '${workEffortType}: ${workEffortId} created
successfully' would be more generic and convenient.
> 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
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9516) User should be notified with success message on Creating New Routing
[ https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101275#comment-16101275 ] Sonal Patwari commented on OFBIZ-9516: -- Hello Pranay Thanks for the review, I think we can update the success message as '[WORKEFFORT_ID] created successfully'. So that would be applicable wherever 'createWorkEffort' service is used. Thanks! > 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 (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9365) Screen rendering error on Content Advanced Search page
[ https://issues.apache.org/jira/browse/OFBIZ-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-9365: Assignee: Sonal Patwari (was: Aditya Sharma) > Screen rendering error on Content Advanced Search page > -- > > Key: OFBIZ-9365 > URL: https://issues.apache.org/jira/browse/OFBIZ-9365 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Sonal Patwari >Priority: Trivial > Attachments: screenshot-1.png > > > Steps to reproduce: > 1. Go to Content component > (https://demo-trunk.ofbiz.apache.org/content/control/main) > 2. Click on Content from > submenu.(https://demo-trunk.ofbiz.apache.org/content/control/findContent) > 3. Click on the Advanced Search button > (https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions). > 4. Provide Content Id and click on Find button. > It gives a ScreenRenderException. > The error only occurs when Content Id is provided to refine the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9519) User should be notified with success message on Update Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9519: - Attachment: OFBIZ-9519.patch Provided patch in the attachment. Solution : Created a new uiLabel to print success message and returned it as success message from 'updateQuote' service. > User should be notified with success message on Update Quote page > - > > Key: OFBIZ-9519 > URL: https://issues.apache.org/jira/browse/OFBIZ-9519 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Sonal Patwari >Priority: Minor > Attachments: OFBIZ-9519.patch > > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Click on Quote link from the submenu > (https://localhost:8443/ordermgr/control/EditQuote?quoteId=CQ0001) > 6. Make changes and Click on Submit button. > No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9516) User should be notified with success message on Creating New Routing
[ https://issues.apache.org/jira/browse/OFBIZ-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-9516: - Attachment: OFBIZ-9516.patch Provided patch in the attachment. Solution : Created a new uiLabel to print success message and returned it as success message from 'createWorkEffort' service. > 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: Sonal Patwari >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 (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-7462) Required Field Indicator (*) / Form Validation is missing on Create New Data Source Form
[ https://issues.apache.org/jira/browse/OFBIZ-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari reassigned OFBIZ-7462: Assignee: Sonal Patwari > Required Field Indicator (*) / Form Validation is missing on Create New Data > Source Form > -- > > Key: OFBIZ-7462 > URL: https://issues.apache.org/jira/browse/OFBIZ-7462 > Project: OFBiz > Issue Type: Improvement > Components: marketing >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Sonal Patwari >Priority: Trivial > > Form Validation / Required Field Indicator \(*\) is missing on Create New > Data Source Form . > Marketing -> Data Source -> Create Data Source -> Data Source Id -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-7496) Require check on Create Work Effort Screen
[ https://issues.apache.org/jira/browse/OFBIZ-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-7496: - Attachment: OFBIZ-7496.patch Provided patch in the attachment. Solution : EditWorkEffort form in WorkEffortForms.xml does not have required check for WorkEffort Name. Hence added required-field = 'true' for WorkEffort Name field. > Require check on Create Work Effort Screen > -- > > Key: OFBIZ-7496 > URL: https://issues.apache.org/jira/browse/OFBIZ-7496 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Avnindra Sharma >Priority: Minor > Attachments: OFBIZ-7496.patch > > > Require proper client side validation check on create work effort screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
