Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
|
|
159 KB
|
|
165 KB
|
|
441 KB
|
|
251 KB
|
|
443 KB
|
|
256 KB
On exit of create dialog the list is modified by adding the job information that was just created. The issue is that the job you are creating is failing. The database information is holding the correct information so a refresh of the list will show you that the job actually is disabled. The list information is showing enabled because we added the item from the dialog information and not from a database object refresh. For now you can just refresh the list to have the correct information. Looking into the design change to fix this...
Once the job is created the job information will be extracted from the database instead of the dialog before added to the list. If the job is created but parameters are set differently due to database restrictions they will show correctly on screen now.
Once the job is created the job information will be extracted from the database instead of the dialog before added to the list. If the job is created but parameters are set differently due to database restrictions they will show correctly on screen now.
@abhishek, pls go through Ivans comments and verify with the latest v15 build
@abhishek, pls go through Ivans comments and verify with the latest v15 build
@Tariq: I went through the steps suggested by Ivan,and I have observed the following changes.
Here are the steps which I followed:
Case A:
I created a job with enable option checkbox marked as “unchecked”. That is job is created with enable option set to False.
Case B:
When altered the job, I marked the enabled option checkbox as “checked”. That is job is altered and enable option is set to TRUE.
Please refer screenshot1.jpg
Here it is observed that when the enable option checkbox is marked as “checked”, in Enabled column, it shows that the job is set to TRUE. This is right.
Please refer to screenshot2.jpg
But when we alter it again the enable option checkbox appears to be “unchecked”.
Expected Behaviour: It should be marked as checked.
Please refer to screenshot4.jpg
Case C:
When we click on refresh icon, the Enabled column value which was set to TRUE changes to FALSE.
Expected Behaviour: When we click on refresh icon, the Enabled column value should not set to FALSE.
Please refer screenshot 3.jpg
Case D:
It is also observed that when we create a job with enable option marked as checked. And when we alter it and set the enable option as unchecked, in Enabled column value it shows False and when we refresh, it does not changes to True.
@Tariq: I went through the steps suggested by Ivan,and I have observed the following changes.
Here are the steps which I followed:
Case A:
I created a job with enable option checkbox marked as “unchecked”. That is job is created with enable option set to False.
Case B:
When altered the job, I marked the enabled option checkbox as “checked”. That is job is altered and enable option is set to TRUE.
Please refer screenshot1.jpg
Here it is observed that when the enable option checkbox is marked as “checked”, in Enabled column, it shows that the job is set to TRUE. This is right.
Please refer to screenshot2.jpg
But when we alter it again the enable option checkbox appears to be “unchecked”.
Expected Behaviour: It should be marked as checked.
Please refer to screenshot4.jpg
Case C:
When we click on refresh icon, the Enabled column value which was set to TRUE changes to FALSE.
Expected Behaviour: When we click on refresh icon, the Enabled column value should not set to FALSE.
Please refer screenshot 3.jpg
Case D:
It is also observed that when we create a job with enable option marked as checked. And when we alter it and set the enable option as unchecked, in Enabled column value it shows False and when we refresh, it does not changes to True.
Steps, alter job... sql sent... window closed... catalog data refreshed...
you click on alter again and the catalog tables are requeried and if in between the extraction oracle changes values in the catalog tables, then it changed back to disabled. I can create jobs this way here and observe what is happening to you but the issue isn't that ads isn't displaying the DATABASE information correctly. The issue is that the database is changing values within a second after our refresh has happened.
Will reassign to niels but I don't think there is much we can do... we can't constantly extract data if the database decides to change values...
Steps, alter job... sql sent... window closed... catalog data refreshed...
you click on alter again and the catalog tables are requeried and if in between the extraction oracle changes values in the catalog tables, then it changed back to disabled. I can create jobs this way here and observe what is happening to you but the issue isn't that ads isn't displaying the DATABASE information correctly. The issue is that the database is changing values within a second after our refresh has happened.
Will reassign to niels but I don't think there is much we can do... we can't constantly extract data if the database decides to change values...
Issue #10264 |
| Closed |
| Incomplete |
Completion |
| No due date |
| No fixed build |
| No time estimate |
On exit of create dialog the list is modified by adding the job information that was just created. The issue is that the job you are creating is failing. The database information is holding the correct information so a refresh of the list will show you that the job actually is disabled. The list information is showing enabled because we added the item from the dialog information and not from a database object refresh. For now you can just refresh the list to have the correct information. Looking into the design change to fix this...