2. add 'headerItem' as communicationevent list item link's parameter for height light menu bar
3. fix 'assign to me' buttom shifts to the left.
4. add related company button and form for create new related company in lead and contact.
5. add email buttons in sfa's communication event
6. add lookup screen and form for account lead.
7. fix telecomNumber display format. look ListWorkEffortContactMechs as example
8. rename button 'assign existing account lead' in leads to 'add related company
9. remove assigning existing account in contact
10. on all screens add a 'find' button to go back to the find screen
11. When click on comvert lead, show the message: 'Please first add related company' when company is empty
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@834010 13f79535-47bb-0310-9956-ffa450edef68
2. add 'email address', 'telephone number', 'city', 'country', 'company' field to list.
3. Accounts and Leads, the opportunity box have a link to the actual opportunity in sfa
4. viewing a communication event in SFA should have a reply/replyall/new email button which links to an new email request in 'mycommunciations' in party
5. remove party's status field from list (always active)
6. Account Lookup screen replaced ftl by forms.
7. change name of party's statusId field in PartyRelationshipAndContactMechDetail view called 'partyStatusId' because It be orverrided by relationship's statusId.
8. delete unuse ftl file,screens, forms, request and view map.
9. combined partyname and id in one field
10. changed the performfind service with a notequal operation that a null value is also not selected.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@832694 13f79535-47bb-0310-9956-ffa450edef68
1. New SFA Account/contact/lead find/list screens replacing ftl/partysearch with form/performfind.
2. SFA now compatible with the party manager with the 'all' option still have the previous 'my' option
3. added new widget property: 'text find' to set the default here and not in the xsl
4. added 'container' as a field to the form in order to insert forms dynamically with an ajax request
5. fix bug for using radio field.
6. Implemented comments on this jira issue including using the find decorator
Contribution by Chattree, an employee of Antwebsystems Co.Ltd.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@832294 13f79535-47bb-0310-9956-ffa450edef68
2 issues :
* URL was not secured in FTL
* StateProvinceGeo is not mandatory (maybe there are others, too late too check..)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@829460 13f79535-47bb-0310-9956-ffa450edef68
I was planning to wait longer, but I can't wait more. I have added a lot of small trivial changes in this patch and they are blocking me to go further on other issues...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@813307 13f79535-47bb-0310-9956-ffa450edef68
A new help system is implemented which is compatible with the current system which uses the ofboz.docs.org site to store the data.
The new help system has a number of advantages over the old version:
1. complete multilanguage without config xml files, using the locale.
2. Having an automatic multilevel index of all help pages using the ContentAssoc entity
3. Using the content manager for retrieval.
4. Template driven, aware of the different visual themes.
5. A first step towards the storage of OFBiz documentation within the OFBiz system itself.
6. Easy update via normal svn in seed data.
7. Aware of portlets on (userdefined) Portal pages.
8. Create awareness of the capabilities of the content component
The reason of this development was the requirement to provide user documents to the customers of Antwebsystems Co.Ltd
Some of the possible extensions could be:
1. a search function
2. print all or specific help files in PDF format
3. make the help screens work better with the business theme
4. Explain how help can be extended
5. In the help screen be able to send a message to the local support team
6. But most of all, create more help content!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@804546 13f79535-47bb-0310-9956-ffa450edef68
In this patch the "Edit" & "Expire" button is not shown when thruDate < nowTimeStamp.
Thanks Divesh for your contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@786373 13f79535-47bb-0310-9956-ffa450edef68
I have provided default value in fromDate field while creating new record. Because after saving it returns to the same screen and it shows empty value for fromDate field. User can change fromDate manually if he / she would prefer to do this.
Thanks Divesh, Ratnesh for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@786016 13f79535-47bb-0310-9956-ffa450edef68
As per the discussion on the above jira issue following things were finalised:
-- Show both the status (roleStatusId & statusId) in report.
-- Also added the roleStatusId field for filtering.
Thanks Awdesh, Ratnesh, Mridul & Hans for sharing views on this issue.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@784152 13f79535-47bb-0310-9956-ffa450edef68
As it is not good practice to keep two request same and change the case only (For ex: we have CreateLead & createLead).
I think it creates ambiguity.
The best practice(as far as I learned) is to use "New" prefix for all the request if you are using the form only to create a record.
Although if you are using the same form for create & update then you should add "Edit" prefix before each request.
SFA will be bit large very soon so its safe to remove such issues in early stage.
Here is the code snippet :
<request-map uri="CreateLead">
<security https="true" auth="true"/>
<response name="success" type="view" value="CreateLead"/>
</request-map>
<request-map uri="createLead">
<security https="true" auth="true"/>
<event type="service" invoke="createLead"/>
<response name="success" type="request" value="viewprofile"/>
<response name="error" type="view" value="CreateLead"/>
</request-map>
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@767904 13f79535-47bb-0310-9956-ffa450edef68
[ \t]+$ => "" (empty)
Should be easier to review when committing changes with trailing spaces removed automatically by anyedit or such tool (please refer to http://docs.ofbiz.org/x/mg)
Of course this effort to remove trailing spaces has no functional implications.
Actually, I was doing a 1st commit and as it's long to upload, I got conflicts with r763135
In the meantime I did some refactoring also in *.java and *.groovy files :
){ => ) {
if( => if (
while( => while (
}else => } else
else{ => else {
switch( => switch (
try{ => try {
}catch => } catch
catch( => catch (
}finally{ => } finally {
So these changes are also in this commit, should not be a problem anyway.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@763175 13f79535-47bb-0310-9956-ffa450edef68