Skip to main content

Qlik

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Suggest an Idea

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

ABILITY TO ABORT THE TASK WITH OUT UPDATING THE DOCUMENT WHEN CRITERIA NOT MATCH

fmcrashid
Contributor II
Contributor II
‎2020-06-11 10:59 AM

ABILITY TO ABORT THE TASK WITH OUT UPDATING THE DOCUMENT WHEN CRITERIA NOT MATCH

Attachments
AbortDoesNotWork.qvw

We need the ability to "Abort" the current qlikview load(Task) with the following consequences:

1 - Do not save the file (leave the old file intact)

2 - Do not trigger the dependent workflows in the QMC

3 - Do not distribute the bad file In our current process,

by “failing” the workflow using a bad command, ALL THREE of these requirements are met but large number of intentional failures affect system performance

Status: Closed - Already Available Submitted by Contributor II on ‎2020-06-11 10:59 AM
Labels
843 Views
3 Comments
Vinay_Kapoor
Employee
Employee
‎2020-11-09 08:58 AM

Thank you for your feedback and keep it coming! We have not added this one to the backlog as a partially executed task can leave a document in states that are difficult to recover from. You can achieve something similar using instructions here https://support.qlik.com/articles/000002664 and using our TFS integration https://community.qlik.com/t5/QlikView-Documents/Qlikview12-Source-Control-with-Team-Foundation-Serv...

Status changed to: Closed - Already Available
fmcrashid
Contributor II
Contributor II
‎2020-11-09 09:23 AM

Hi Vinay

you comments and the suggested articles are completely irrelevant to the idea proposed here. You might has mistakenly added articles and have closed it. This should be stay open. please have a look at it.

Yuliya_Kiperberg
Employee
Employee
‎2021-09-27 09:26 PM

Hi @fmcrashid,

Thank you very much for your feedback, we really appreciate it!

For your points 2 & 3 (2 - Do not trigger the dependent workflows in the QMC & 3 - Do not distribute the bad file In our current process), we recommend the use of triggers and task dependencies. In QlikView, we have the ability to use triggers and task dependencies to set up sequential and dependent tasks. Task dependencies can ensure that the task only runs if other tasks have successfully completed. The trigger would not work unless the dependencies have been met. 

For more information regarding triggers, please take a look at the following link: https://help.qlik.com/en-US/qlikview/May2021/Subsystems/QMC/Content/QV_QMC/QMC_Documents_SourceDocum...

For more information regarding task dependencies, please take a look at the following link: https://help.qlik.com/en-US/qlikview/May2021/Subsystems/QMC/Content/QV_QMC/QMC_Documents_SourceDocum...

As for "1 - Do not save the file," that would depend on the task itself. For example, once the data has been reloaded in a task, we wouldn't be able to revert to the previous data. This is not something that fits our roadmap and not something we’re looking to invest in at this time.

Thank you!

-Yuliya Kiperberg

 

Subscribe by Topic