AwareIm does not have the ability to merge the work of different configurators (or developers) or versions. Until our friends at Aware get to that feature the following work process is followed by our developers; - An Acceptance version exists. - Each Developer has their own development version (space) 1. Export the Acceptance Version into bsv and xml formats. 2. Load and lock your own development version 3. Import the Acceptance Version into the development version. This way you have all the current functionality available to you, including the features added by the other developers. 4. Add functionality (such as new entity or new rule etc) 5. Add test processes (such as creation of test data etc) 6. Do ‘unit’ testing and functional testing until functionality is ready. 7. Export development version in XML format and compare with previously exported (step 1) acceptance version (using your favourite diff tool). The diff result can be used as a kind of development log to assist you remember what you have done in this development session. 8. Load and lock Acceptance version (only one developer at a time can do this) 9. Copy new functionality to the acceptance version. Copy and paste can be done as long as it is done in the right sequence. Eg. a new attribute is created in an Business Object (BO) and a rule is developed using that attribute. Therefore the field must be copied first, before the rule. 10. Ensure that any test processes are also copied. 11. Run ‘unit’ and functional testing on Acceptance version. 12. Unlock Acceptance version. 13. Back to step 1. A good intermediate wish list item would be the ability to [b]import[/b] [b]XML[/b] business spaces. (And not just export to XML.) That way, we can use a diff and merge tool in the following sequence: 1. Export Acceptance and import into own development space 2. Do development and testing 3. Lock Acceptance and export to XML 3. Export Development space to XML 4. Do diff and merge 5. Import the merged XML to Acceptance 6. Unlock Acceptance The eventual wishlist item would be the ability to select two (unpublished) versions of a business space, and run a merge process into a new version. I hope we see something like this soon, but I have seen comments in this forum about this subject since 2005.... AwareIM is a tremendous tool and the bigger development shops are bound to take it seriously once "enterprise" features such as this start becoming available.

I have joined a company that needs to rebuild multiple applications in a newer technology and I believe that Aware IM would be ideal, but we will need to be able to have multiple developers working on the same application/business space. [size=150][b]This is currently stopping us buying and using the Aware IM[/b][/size]. I believe that pniehaus's idea is possibly a viable option if tweaked slightly. Add ability to [b]import [/b]XML business spaces. (not just export to XML.) Therefore use a diff & merge tool in the following sequence: [b]1.[/b] Export Initial Business Space version to XML files. [b]2.[/b] Store XML Files in[b] source control[/b]. [b]3.[/b] Developers [b]Import the XML[/b] into their own development business space, including updating the data structures - if changed. [b]4.[/b] Do development and unit testing [b]5.[/b] Export to XML [b]6.[/b] Merge/Check in XML files into[b] source control[/b]. With XML export and import of business spaces in place I believe that this would open a number of possibilities where multiple developers/configurators are required. Regards, Tim

Multiple configurators, developers, Merge versions

pniehaus

AwareIm does not have the ability to merge the work of different configurators (or developers) or versions.

Until our friends at Aware get to that feature the following work process is followed by our developers;

An Acceptance version exists.
Each Developer has their own development version (space)
Export the Acceptance Version into bsv and xml formats.
Load and lock your own development version
Import the Acceptance Version into the development version. This way you have all the current functionality available to you, including the features added by the other developers.
Add functionality (such as new entity or new rule etc)
Add test processes (such as creation of test data etc)
Do ‘unit’ testing and functional testing until functionality is ready.
Export development version in XML format and compare with previously exported (step 1) acceptance version (using your favourite diff tool). The diff result can be used as a kind of development log to assist you remember what you have done in this development session.
Load and lock Acceptance version (only one developer at a time can do this)
Copy new functionality to the acceptance version. Copy and paste can be done as long as it is done in the right sequence. Eg. a new attribute is created in an Business Object (BO) and a rule is developed using that attribute. Therefore the field must be copied first, before the rule.
Ensure that any test processes are also copied.
Run ‘unit’ and functional testing on Acceptance version.
Unlock Acceptance version.
Back to step 1.

A good intermediate wish list item would be the ability to import XML business spaces. (And not just export to XML.) That
way, we can use a diff and merge tool in the following sequence:

Export Acceptance and import into own development space
Do development and testing
Lock Acceptance and export to XML
Export Development space to XML
Do diff and merge
Import the merged XML to Acceptance
Unlock Acceptance

The eventual wishlist item would be the ability to select two (unpublished) versions of a business space, and run a merge process into a new version.

I hope we see something like this soon, but I have seen comments in this forum about this subject since 2005....

AwareIM is a tremendous tool and the bigger development shops are bound to take it seriously once "enterprise" features such as this start becoming available.

ACDC

A while back I had some dialogue going with support regarding developing a merge feature. At the time they seemed willing to build this feature for a price. Maybe we should pursue this by raising some money for the project.

pniehaus

I do not wish to criticise this product, because I am blown away with it. However the marketing at http://www.awareim.com/features.html#ChangeControl and "Build applications that work well on corporate IT infrastructure" etc, etc implies a heavyweight/enterprise tool. Enterprise implies many developers... and many developers require change control. It is difficult enough with automated tools, but with no tools at all....

ACDC

I am sure there is a long feature list that is being worked on by support, however if you wish for a feature to be placed on top of their To-Do list it normally requires some money to motivate them. Also they are very efficient with this regard

A number of features that exist in the product today come from users paying for development. In some cases a number of users have chipped in to make it happen.

So if this feature would increase the productivity in your team it would make sense to fund part of the development. I am sure others may be interested in chipping in

pniehaus

Again, not wishing to criticise:
"Enterprise" in the marketing should equal "Enterprise" in the product.
Paying for an upgrade (or paying an annual license fee) is the normal way to finance new features. If I exclusively have to pay for a new feature, I would expect exclusive use of it.

I however do not have a problem to pay for it as long as nobody else gets charged for the same feature. I believe an upgrade charge/annual fee is however applicable with this product.

This "feature" does not appear on the wish list, why not? Are there only 2 customers that want it?
My suggestion to Aware would be to place it on the wish list, identify the "must have" customers, and make an offer to those customers.

ACDC

suggestion to get the ball rolling, why don't you write up a specification for this feature and send it via email to support@awareim.com requesting they quote on the custom development

Then once you have the quote, place a notice in the forum to see how many are prepared to "chip in" for the feature

Timo

There are definitely more than two customers and potential customers that wish to have multiple configurators, developers working on the same business space.

I can certainly understand where the issue are in merging the changes from multiple developers, and this is not as trivial as merging text files as most change control systems do. Aware IM is configured in data and would require a fair amount of thought/design to accomplish proper merging.

Maybe being able to lock individual business objects, reports, etc... would help.
Although when you add a relationship from one business object to another both objects are updated and therefore you would have to lock both of these.

having pointed out the above I would still like to see either:
- the ability for multiple configurators, developers working on the
same business space
- or some form of merge from branched versions.
(differences from when the branch was created)

Timo

I have joined a company that needs to rebuild multiple applications in a newer technology and I believe that Aware IM would be ideal, but we will need to be able to have multiple developers working on the same application/business space.

This is currently stopping us buying and using the Aware IM.

I believe that pniehaus's idea is possibly a viable option if tweaked slightly.

Add ability to [b]import [/b]XML business spaces. (not just export to XML.)
Therefore use a diff & merge tool in the following sequence:

1. Export Initial Business Space version to XML files.
2. Store XML Files in source control.
3. Developers Import the XML into their own development business space, including updating the data structures - if changed.
4. Do development and unit testing
5. Export to XML
6. Merge/Check in XML files into source control.

With XML export and import of business spaces in place I believe that this would open a number of possibilities where multiple developers/configurators are required.

Regards,

Tim