saravananm - Monday, June 29, 2009 7:28 PM:
Hi There,
This is a great site and a nice product.
I'm evaluating the 'Variant' feature availalble with Aras community solution.
I'm able to import the variant 2.1.aml file and look at parts/variants/bom etc for the sample product 'tractor'. When trying to use the order option and confiure the sample item 'tractor' , the configurator doesn't show up and prompt me to enter pick the options.
I tried portfolio/order/new, tractor as the TLA, the screen doesn't come up with the configurator and doesn't produce any errors either.
Please let me know if I didn't provide enough details and need more info, I hope it is a simple setup issue.
Thanks.
Saravanan.
PeterSchroer - Tuesday, June 30, 2009 9:19 AM:
Hello Saravanan,
I was the original author of the Variants solution (using a cool idea from Will Watson of the GSI Group as the initial seed). I'll try to help you. Over the past 6 weeks we have invested alot of time in the Variants solution for Kieper, a manufacturer of car and airplane Seats. I've been short on time, so we have not yet posted the update to the Community Projects site. Do you have an existing Variant / Options configurator that you are replacing, or do you have documented requirements that you can share? Or was this an academic curiousity.
If you are interested in evaluating this package, I can give you a hand resolving the installation issue, and would be happy to give you a demo of the changes implemented for Keiper to see if these would interest you. Feel free to contact me directly [email protected]
Peter
Elin - Wednesday, April 28, 2010 4:39 AM:
saravananm,
Did you ever find a solution to your problem? I have the exact same problem.
I had however also a problem importing the package and got one error on 29 out of 31 which could be the source of the problem (I used the build 4.0 of the solutions upgrade tool in combination with Aras 9.1.0).
Anyone out there with a solution to the problem with loading the configuration box with the BOM?
saravananm - Tuesday, June 30, 2009 11:52 AM:
woec - Wednesday, November 4, 2009 4:29 AM:
Hello Peter,
at this time we are evaluating ARAS for use in our company. One of our goals for use the ARAS system would be the variants / product configurator topic. I installed the your demo database package for testing, which includes the variant package you wrote, to get some taste of its capabilities. At the moment I feel it could be customized/expanded to our needs. From your post above, I read you have developed this package further meanwhile. Maybe the actual state of the package could be interesting for us.
From playing around with the 2.1 version of the variant package I found some issues I could not get working:
- Inserting a 2nd (boolean ored) rule to a BOM position in a variant item (I found such entries in the tractor example you supplied);
additional question: is there a possibility to insert boolean and type rule conditions?
- using the codeset rule type, one can build complex formulas, but there I found no possibility to connect list type exclusive or conditions (currently all codeset options are displayed in the order context); also NOT type conditions are currently not possible.
Please comment. Thanks
woec
saravananm - Wednesday, April 28, 2010 10:48 AM:
Elin, Thanks for checking, I was not able to go any further and stopped there after. Saravanan.
PeterSchroer - Wednesday, November 4, 2009 9:04 AM:
Hello Woec,
I have not posted the updates yet... there is some work involved in re-packaging them due to some signiifcant customer-specific rules I need to rremove. I am hoping that the programming work will get slower at the end of the year, and then I will have time. I am happy to work with you directly in the mean-time though. I will send you a separate Email on how to get a copy of the work-in-progress.
I have heard from one other person about the problem inserting a 2nd rule onto a BOM position. Obviously this worked in the past, because the demo data shows 2 rules on one part. So we can assume this was easily broken while experimenting with something else, so it should be also easily fixed. I will take a look. If I fix this one bug, I'll post the solution (but without the new advanced featuers).
The codeset rule was completely modified during the project with Keiper. They added lots of new behaviors, some pretty exciting stuff. These are the enhancements that I want to re-package and post to the community. I don't beleive they had NOT conditions, however the Boolean processor was completely re-written for Keiper, and it is now easily to add new types of Boolean expressions. XOR and NOT should be possible now.
Peter
