Since upgrading to iMIS 20.1.13 (from 15.x) users have been encountering a Customer Portfolio shutdown we have traced to a new clustered primary key for dbo.Name_Indexes. The primary key is "PK_Name_Indexes". This primary key did not exist in iMIS 15.x. The stored procedure "sp_asi_UpdateNameIndex" executes against dbo.Name_Indexes. It is unchanged between 15.x and 20.1.13, and will now occasionally fail because violations to this new primary key.
sp_asi_UpdateNameIndex failing due to new clustered primary key for dbo.Name_Indexes (PK_Name_Indexes)
we're working on custom conference registration iPart mainly using SOA EventManager to register members for various event functions. There is a number of Registrant classes for the event and registrant can belong to more than one so we need to do the following:
1. Determine lowest price for registrant for each selected function or option. I was able to do that using iBO CFunction.GetFuncFeeByRegClass(registrantClass)
I am going round in circles with support on this one and cannot get a coherent answer so I thought I would try you folks.
I have an iqa that is returning the names of contacts that are set up as organizations.
I would like the results to be available in a drop down list for selection on a contact/customer additional window so that the users can select the organization the contact works for (we cannot use the company field as our contacts can work for multiple organizations so we have a custom multi instance table to capture their employers.
You may have recently found that all the multi-value look up fields in the iMIS desktop have stopped working, and give an error:
"Duplicate description detected. Please correct the lookup table."
This seems to be caused by a recent MS Update - KB3008923
Once this update is removed, the look ups should work.
I'm browsing SOA documentation for last couple of hours trying to figure out how to retrieve Auto-Enroll flag for event function. There is nothing in EventFunctionData class.
Only place I could find it is in EventData.RegistrationOptions but that collection is empty for my test event.
Does anyone know how to get this flag?
In the process of processing orders this morning we found that our printers are not working, and so all of the reports that print as part of the process of processing orders did not print. Unfortunately, all of the orders were moved through the process. My question is this: how do I recreate the papers that should have printed at each step of the order processing process? I've got the list of order numbers, I'm just not sure what to do with them.
When processing orders this morning an incorrect date was entered. Now, instead of having a ship date of 11/30/2014 we have a ship date of 12/30/2014. This is keeping reports from running correctly. I'm wondering if I can just update the ship_date_time field in the Orders table or if this will not cover all the bases. Are there other feidls/tables that would need to be updated?
We received this email overnight from payflowpro.
I'm trying to understand if iMIS uses SSL3 to integrate with payflowpro and what if any steps need to be done to swap to TLS?
Does anyone know?
From: Newport, Billy Anne [mailto:email@example.com]
Sent: Tuesday, 25 November 2014 6:36 AM
Subject: Immediate Action Required – SSL 3.0 vulnerability
Immediate Action Required – SSL3.0 Vulnerability
On Tuesday, October 14, 2014, details were released about a vulnerability to version 3 of Secure Sockets Layer (SSL 3.0). Since that time, PayPal has been hard at work to mitigate any potential impact to our merchants.
To help mitigate risk associated with this vulnerability, PayPal will discontinue support for SSL 3.0 on December 3, 2014 at 12:01 a.m. Pacific Standard Time. Unfortunately, this necessary step may cause compatibility problems resulting in the inability for customers to make purchases on your site or other processing issues.
We wouldn’t have been able to extend our support of SSL 3.0 to December 3, 2014, at 12:01 a.m. PST if we hadn’t also been able to take significant steps to migrate the risk of this vulnerability for our merchants. We want to assure our merchants we have seen no evidence that the SSL 3.0 issue has led to any compromise of security at PayPal.
Keeping our merchants’ accounts and data secure is PayPal’s top priority and a guiding principle when we make challenging decisions, like this one.
We’re here to help our merchants through this process. We’ve put together a comprehensive Merchant Response Guide to ensure systems are secure from this vulnerability.
What do I need to do?
If you don’t manage website integrations for your business, we strongly encourage you to work with your website service partner (developer, hosting company or e-commerce platform, etc.) and share the Merchant Response Guide, which provides the basic guidelines on how to update to Transport Layer Security (TLS). If your website service has questions or need support, advise them to contact our Merchant Technical Support.
Thank you for your prompt attention to move this issue and understanding of our approach. Though we recognize this necessary step may cause compatibility issues, we can’t stress enough that this short-term inconvenience is heavily outweighed by our joint promise to our respective customers that we will keep their accounts and financial details safe. We plan to keep our customers up to date on how we are addressing this issue via the appropriate channels, including PayPal Forward, our Twitter handle, Customer Service and for merchants, through our Merchant Services team. We appreciate your patience and understanding as we work around the clock to better serve you and keep you and our consumers safe.
For technical assistance, please call the Pay flow Support Team at (888) 883-9770 and select option 2. They will be able to direct your call to our dedicated team of engineers who can help answer your questions. Our engineering resources are available Monday thru Friday from 8:00am to 6:00pm CST.
Billy Anne Newport
Merchant Outreach Business Consultant
I am having a play with the Join Now feature that is in the v20 web pages. However, I cannot see where I can set the member type it should use when it does the contact create. I have created an Applicant Join Now button, product and bill cycle and I can get the contact in and the charge into their cart. but where can I set the member type that it should use when it creates the contact record? We do not have the acquisition module so I am wondering if it is in there - but I am also looking for the doc on that feature and there is nothing in the doc site.
I thought it would be fairly straight forward to create a set of committees for our provincial council committees, add users to the committee and then give the council their own page (like the community page) secured from the public and members on the web site - apparently not.
We have a council made up of several different committees. I would like to have the committees defined and the members added to their appropriate committee (some are one more than one committee)