[jira] [Commented] (OFBIZ-8358) Validation missing on required fields on run service screen

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-8358) Validation missing on required fields on run service screen

Nicolas Malin (Jira)

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

ASF subversion and git services commented on OFBIZ-8358:
--------------------------------------------------------

Commit 8ef589607710368d7657c8e0a3285fe2e681abcf in ofbiz-framework's branch refs/heads/release17.12 from bjugl
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=8ef5896 ]

Fixed: Service calls of "createPartyContactMech" now include the needed contactMechTypeId (OFBIZ-12175) (#292)

This was broken by OFBIZ-8358 where, as well explained at OFBIZ-12175,
"createPartyContactMech Service has been changed to expect an
OUT contactMechTypeId paramter and the call on this end has not been modified."

Conflicts handled by hand in PartyServices.java
I let the changes coming from trunk, too much to revert by hand


> Validation missing on required fields on run service screen
> -----------------------------------------------------------
>
>                 Key: OFBIZ-8358
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-8358
>             Project: OFBiz
>          Issue Type: Bug
>          Components: ALL COMPONENTS
>            Reporter: Avnindra Sharma
>            Assignee: Deepak Dixit
>            Priority: Major
>             Fix For: 16.11.01
>
>         Attachments: screenshot-1.png
>
>
> To regenerate:
> 1) Navigate to service engine and select any service, eg: createPartyRelationship.
> 2) Run the service while existing required field on  schedule job screen.
> Service will not run as the proper validation is not there for it.
> Please refer the screenshot.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)