Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ŁukaszBachman last won the day on April 19 2019

ŁukaszBachman had the most liked content!

Community Reputation

16 Good

About ŁukaszBachman

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

998 profile views
  1. No extra configuration should be required, I think. I would try to compare URLs generated by Connect with proxy OFF and ON. That should give you an idea where the URL rewrite is broken. If you tell us what that place is, we will try to further investigate. Without knowing which URL is rewritten and how we can't really do much. Obviously you could replace your production URL with some placeholder value.
  2. Hi Lancenudd, Which proxy configuration file are you referring to? Over the years we've seen few customers using proxies and if it worked out of the box depended on the proxy being used. Sometimes they ran into small UI limitations (ex. icon not rendering fine due to wrong URL rewrites), but in general it was working fine. Can you further describe in details the problems you are seeing with redirections?
  3. Hi Fuzed, I just replied to your support ticket, where you posted the same problem. I did few tests on my own and I don't see any issues with the software, so I think it may be a problem with choosing the wrong settings. You can change date formats to any custom one. This is described in section "15.2.11. Load file options" if Connect User Manual. Sorting options are described in "15.2.17. Reports and ordering". Hope you will be able to figure this one out!
  4. Hi Jason, I agree with you and I'm happy to announce that next version will get following improvements: Ability to edit tag's parent New permission allowing to create new tags (granted to everyone by default) New permission allowing to edit tags (granted to everyone who already had ability to delete tags from created by other reviewers)
  5. Hi Neil! I noticed that the exact same thing was reported in. We already have an internal ticket about extending this functionality, it just needs a bit of time to get into a development queue. Thanks for pointing that out!
  6. @Jared, I think that this will get created if you create an Export Set while running your production. Intella will add a new column then which you can see in Items Table or use in further exports.
  7. Hi again, What you can try to do is to extend the default timeout of 3 minutes to a larger value by means of trial and error (4, 5, 6 mins...). To do this one has to modify "C:\Users\ACCOUNT_RUNNING_CONNECT\AppData\Roaming\Intella Connect\prefs\user.prefs" file by adding the following line: ReverseProxyTimeout=XXX where XXX is the new value in milliseconds (defaults to 180000). Intella Connect restart would be required. In general it should be ok to do this, but keep in mind that such timeouts are added for a reason and setting this value too large can result in performance degradation if not used wisely.
  8. Hello Stephan, This all sounds like good ideas to me, I'll include them in our roadmap for the future. We have some long-term plans for improvements in overall experience of using tasks in Connect, where I would like to address these as well. Leveraging Nodes for background tasks is also something that we are planning to do, but that one will be the hardest to do. Thank you for sharing your thoughts and feedback. P.S. Current version allows for stopping (removing) tasks which are running, but this depends on the type of the task (not all of them support this feature).
  9. Hi Margaret! The "Combine queries" option is enforced when there is more than 7 keywords in the list. We made this decision so that you don't evaluate all 98 keywords at once, which will likely not be of much use. That being said, please note that Intella Connect 2.3.1 will allow you to explore your keyword list and search for individual queries contained in it. Here is a relevant snippet from the Release Notes:
  10. I renamed the button to "Finish source management", to avoid confusion. This change will be present in upcoming 2.3.1 release.
  11. Hi Tom, Indeed we have plans for changing the flow, so that the case will be closed automatically. This requires larger architectural changes to the software, so it will likely take a couple of releases though. However, I do agree with your point about unfortunate naming of this button. We will consider this change in a shorter time span.
  12. Hi Chris, When seeing issues like this it's indeed best to submit a support ticket. Out engineers are working around the clock so often you get a response very vast. Now, what Adam has suggested (reindexing) is actually the best way to ensure that the case indices (databases) have been properly rebuilt. However, it's worth to check indexing logs, Exceptions Report and "Errors" branch in Features Facet beforehand. It will give you a better overview of the state of your case.
  13. Hi Adam! You should note that Primary Dates are calculated based on values stored in Intella columns. Different file formats are populating it differently: sometimes from RAW DATA, sometimes from item properties directly, etc. Therefore I wouldn't go this road because it would be hard to achieve 1:1 consistency. However, I think that the solution to your problem is rather simple. I would create a CSV export (or a load file) containing two columns: Item ID Primary Date Primary date will be populated using full date format (date + time + time zone). Then I'd use some text processing tool (Excel, advanced text editors, etc.) to remove date + time from the 2nd column. Now you'll need to create a new Custom Column of type "TEXT". The final step would be to add a new source as a Load File Overlay with following settings: As you can see the column which you modified (PRIMARY DATE) will be mapped to new custom column you created (TZ ONLY). Item ID is used to match items. After the overlay is imported, you will see: Is that what you need? I hope it helps a bit.
  14. Hello Adam, When using auto-tag feature you can provide the tag name in the following format: parent_tag/new_tag. That way a parent tag will be created first and you should be able to maintain your structure. Is that what you were seeking? As for the other part of your question - what changes/features in the UI you would like to see to influence the scope of this search/tagging operation? Filtering by type or something else?
  • Create New...