<bump></bump>
Hello! I have a notification working for UserRequests that come in afterhours and weekends: SELECT UserRequest AS t WHERE 1=1 AND (TIME(start_date) > '17:00:00' OR TIME(start_date)<'08:00:00' OR DATE_FORMAT(start_date, '%w') IN ('0','6')) That's returning results as expected. I want to either incorporate a clause for Holidays or create a separate notification rule for Holidays but I'm having problems with that OQL. As a test I ran SELECT UserRequest AS u WHERE DATE_FORMAT(start_date,'%Y-%m-%d')='2021-07-05'...
Hello community, I'm trying to find the iTop best-practice for adding SaaS software to the CMDB to be able to associate with Change tickets. For example, Office 365 tenant or Salesforce.com. What kind of CI do you all use to create these types of systems?
Guillaume, that's fantastic. Thanks for the guidance. I can confirm that turning off warnings in the .ini file resolved the issue.
Hello! I have a fresh install of 2.7.3 build 6624. I have the following extensions installed: Approval Process automation V2.0.1 Mail to ticket automation V3.1.1 User Actions Configurator V1.3.5 IPAM for iTop V2.7.0 Network Management Extended V1.0.0 Whenever I navigate to the list of organizations, or contacts I get the error: Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\web\application\displayblock.class.inc.php on line 1734 Warning: Invalid argument supplied for foreach()...
Hi Pierre, thanks for engaging. He does have a Contact in iTop, record number 144. The value in config is set to: 'allowed_login_types' => 'form|basic|external',
We're using LDAP to authenticate our users. All of our agents are signing in with no problem, but one user signs in, and gets the welcome screen. As soon as he clicks on a link, he is prompted to log in again. Once he logs in the second time, he isn't prompted again. This is happening in Chrome, but not IE. All other users are also using Chrome without issue. He has cleared his browser cache. Very odd -- anyone seen this behavior before?
Was coming back in to say that I found that delivery model needed to be set up for me. Thanks for the note Jeffrey!
Same issue. Still searching the forum.
I upgraded to the 2.6.0 beta today for the Tag Attribute. Upgrade went well for any of you who are interested in trying it. I normally would stick to stable releases, but I was really excited about the Tag Attribute. I discovered that the tags are limited to the FAQ class. I'm wondering if there are plans to expand the tags to tickets as well when the stable release comes out? Thanks for the continued work on this great product. This release adds some neat features (still getting used to the new...
Thanks for the response vdumas. It definitely worked in the previous version. We outsource our tier one support and they use autotask. The API would update the friendly name to match the autotask naming convention so all subsequent updates from our partner would update the existing ticket, and I have a scheduled batch job that looks for open tickets in autotask via their API and checks to see if they are closed in iTop (if they were escalated to an internal team). When that condition is true, we...
After upgrading to 2.4.2 my integration script (with autotask) stopped allowing me to update the friendly name via the API. Here's the resposne I get: Reply: Array ( [code] => 100 [message] => Error: friendlyname: Attempting to set the value on the read-only attribute UserRequest::friendlyname ) This worked in 2.3 -- is there a way to make freindlyname not read-only? Thanks.
After upgrading to 2.4.2 my integration script (with autotask) stopped allowing me to upgrade the friendly name via the API. Here's the resposne I get: Reply: Array ( [code] => 100 [message] => Error: friendlyname: Attempting to set the value on the read-only attribute UserRequest::friendlyname ) This worked in 2.3 -- is there a way to make freindlyname not read-only? Thanks.
Still at a loss here. I created a brand new syncronization source in the new version of the software and added a single record. I get the same error message about a null description. Like the previous post, the description value it shows exists. Barring other ideas from you fine folks reading this, my next step will be to try to roll back to an earlier 2.3 release if possible. I know the database schema changed between 2.2 and 2.3 so I can't go back to my original version without restoring the original...
Hello. I just upgraded to version 2.3.4 from 2.2.x. Everything is looking good except I'm getting the following data synchronization error: Unable to create destination object: Object not following integrity rules: issues = Unexpected value for attribute 'description': Null not allowed, class = UserRequest, id = Looking to the right pane of the error detail page though, it shows a non-null value in the description field. There are no special characters or anything. Here's the description: User locked...
I'm trying to set these up as well. Anyone been successful yet?
Resolved my issue -- ran the backup manually, then reran the upgrade procedure without...
I have found the following error in the setup.log: 2016-02-12 16:04:23 - Info - mysqldump...
Hello all, I'm in the process of upgrading to 2.2.1 (2658) and the installer hangs...
I agree that incidents should tie to problems. The way I have understood the difference...
I have a notification that fires off an email when a user request enters the "assigned"...
I'm having good luck with importing and updating tickets into iTop with the Synchronization...
Good morning, I have been successful in creating a data sync with PCs queried from...
Hello community. I cleared one hurdle and found another. I followed a combination...
Okay, thanks for everyone who may have looked at this post and tried to think of...
Hello, I’ve been searching the forum trying to resolve an authentication issue. I...