I have a problem with the function of Clone Test Case, which behaves differently than specified in the manual.
In Test Case, I click on CLONE to open the Filter plan form, and when I click Filter Plan, I get the results table (see. picture).
I miss any button to go back with a confirmed Test plan selection.
If I click to back button of browser, Kiwi TCMS falls and I have to start over again. Please do you have some solution of this, because in manual is different specification.
I expect the test plan selection option.
The Test plan selection is not displayed correctly.
enter image description here
Looks like https://github.com/kiwitcms/Kiwi/issues/695/ which has already been fixed.
Try reproducing on https://demo.kiwitcms.org and report back if it happens, otherwise upgrade to the latest version.
Related
My CN1 based app has been on the App Store and Google Play for a couple of months and works fine but when I rebuild the identical code now on NetBeans locally or through CN1 Build Servers, I'm unable to scroll through the list of containers like before.
The code is similar to the CN1 contacts demo here.
From the .codenameone folder I see.....
UpdateStatus.properties
#
#Fri Mar 27 12:34:19 MDT 2020
CodenameOne_SRCzip=118
CodenameOneJar=118
CodeNameOneBuildClientJar=105
designer=108
CLDC11Jar=108
JavaSEJar=118
lastUpdate=1585334059359
guiBuilder=107
Thx #Shai for the suggestions. A few updates:
Problem still occurred with setAllowEnableLayoutOnPaint(true)
Tested the CN1 contacts list demo and scrolling worked
Primary difference with my code from that demo is that I’m using
URLImage as in the 2nd CN1 example at
https://www.codenameone.com/javadoc/com/codename1/ui/URLImage.html
I was able to get my container of rows to scroll again by removing
any use of URLImage
Tested further by adding a URLImage to certain rows and not to others
As soon as a row is assigned a URLImage it ceases to be a scrollable
contact point for the container. As long as some of the other rows
don’t have URLImages the whole container can be scrolled (when my
finger gets to one of those rows). As soon as I run a trial where
all the visible rows are URLImages, it’s not possible to scroll the
container at all.
I tried to replicate this problem with the CN1 URLImage example
ref’d above but that example links to a nestoria api that seems to
be unavailable now.
Since this still works on code compiled in Jan. but fails for that
same code recompiled now, I still wonder whether something has
changed with my build process but I’ve not been able to replicate
the issue with a CN1 demo.
Will keep this open for now in case there are further suggestions
but I can get by for now by minimizing my use of URLImage (reluctant
to call these URLImages earlier in the app session because a lot of
times the user might not even need these icons).
Thanks,
Mike
No it didn't. Try the contacts demo, it's working right? How is your code different from that.
I'm guessing you're seeing artifacts related to the optimization of setAllowEnableLayoutOnPaint(). To test this in your root form invoke:
form.setAllowEnableLayoutOnPaint(true);
Before showing it. Then see if the problem is resolved. Assuming it is try to find the area that triggers this and follow up with us based on that. Notice that setting this to true has significant scrolling performance implications.
I'm seeing duplicate entries by Step ID in the SSMS Job History Log File Viewer. This is only happening in one of my jobs. In the duplicates, one is marked as complete, and the other as still running.
The duplicate running step has a message with a bunch of version trademark information, nothing helpful.
Any ideas on why I'm getting the duplicated steps in this job, and how to get rid of them?
Check if "Include step output in history" is checked.
Goto your job -> properties -> steps (select one) -> edit -> advanced -> uncheck "include step output in history" if it's there.
Apparently this is a behavior of SSMS version 18. They switched the icon from a ribbon to a green "play" icon whenever you check the "Include step output in history" checkbox. That was very confusing to me too! And in my case, the job step with the extra green play icon has nothing useful in the history details either. It simply has the usual header info and then "Message" with nothing after that (in my case it's a step that runs some Powershell code to update AD). It would be nice to have something after message, pertaining to the job step that ran! But there is nothing useful to me. Be well, Raphael.
To the best of my knowledge, I'm correctly importing my MS-SQL data source in the Control Panel (It says successful in green). I'm also pretty sure I'm importing the data correctly into the Windows 7 Publisher app since I can view the data in the DataView:
but when I go to the Layout View or Run Preview, I just get a blank chart:
It works if I use the default SimulatedTable but once I change the data source to my MS-SQL table, I can't get anything to display, no matter what display element I'm trying to use.
I've tried re-importing the data, using a different MS-SQL table, and re-naming the columns to match the SimulatedTable but it doesn't change the result. Can anyone tell me what I'm doing wrong?
Please try one thing, I am just guessing it might work.
Please select one of the Time Preset buttons and see if you see data in that(where there is blank) chart object.
If yes, then while setting up the time navigator object, select an option in drop down box labeled "Default Time Range Preset"
There are some hacks, please do let me know if run into some weirdness. It might not make sense if i try to explain unless you run into that situation.
Cheers,
I ended up giving up on the Windows 7 version of the application and running a virtual instance of Windows 8.1 instead so I could install the Datazen Publisher app for Windows 8.1. It's FAR less buggy.
Not perfect, though.
We have quite and extensive wizard UI flow and in order to test development changes (e.g.: DOM chanes) at the end of the flow we need to go through all the steps every time since there is data dependancy gathered in previous steps.
This is tedious, takes a lot of time, every time.
Have been thinking about some way of defaulting data but then still we have to click some buttons to get some a-ync data based on the input and press the next btn in the wizard steps.
Using a protractor like behaviour would be excellent. We already have tests set up for that which can take us to the point we need to verify, while developing, in seconds and having all the (stubbed) data in there.
Like to hear your thoughts on this and if such an automated Protractor way of getting to a certain point is possible.
EDIT: why not just use the Protractor test we use on the test server to use locally to go through the development steps and let it stop at a certain point?
While writing the post and re-reading it I answered it in the EDIT with Protractor. Havent tried it yet but should do the trick.
I have a set of SSRS reports developed in Visual Studio Data Tools that are used for several clients.
For one particular site, each report will work perfectly in 'Preview' mode in Visual Studio, however when I deploy them and attempt to run them in IE all of the parameters are disabled/greyed out. I also tried to put in a set of default parameters to see what would happen and when I click 'Run Report' I do not even get the 'Loading' image and the report is just blank.
I have checked the IE security settings and have reset them, and also added the report web page location in to trusted sites which unfortunately hasn't made a difference. One thing I have also noticed is that when I try to view Developer Tools in IE, it also just shows a blank white screen.
I've searched online and found a couple of old posts on various websites with a similar issue but none that were ever resolved, and now I am not sure how to proceed.
More info that might be useful:
The client are using IE 11, it is a terminal server style setup with around 8 or 9 users logged on.
The report I am testing with has 2 date parameters first, and two multi-valued parameters (I have tried other reports but with the same issue)
The client recently moved servers and the reports worked fine before, although it was a fresh install of the report so I don't believe there would be any old settings that could be causing it?
Any help greatly appreciated :)
In SSRS, report parameters can be inactive when the report is generated from a snapshot. Removing this option is as follows:
Navigate to the report in SSRS
"Manage" the report from the drop down.
Select "Processing Options" from the left menu
Is "Render this report from a report snapshot" selected? If so, switch
to "Always run this report with the most recent data" option.
Run the report to determine if parameters are now active.
If this fixes your issue, you may need to switch from the snapshot option to the Scheduled Cache option available under the left menu link "Cache Refresh Options"
For one particular site, each report will work perfectly in 'Preview' mode in Visual Studio, however when I deploy them and attempt to run them in IE all of the parameters are disabled/greyed out.
If that is the case, and a previous version of the report was already on the SSRS report server, what you can do is delete the report, and upload it again. There is some kind of cache for the parameters, that causes that if you modify the order of them, some get disabled, and the only way I have found to get rid of it is to delete the old report from the server.
For me this worked:
Open IE
Go to Settings->Compatibility View Settings
Add the URL of your report server.
You could be experiencing an old bug which was reported a long time ago in a connect item:
SSRS Weird Parameters Order Bug (parameter grayed out)
The official Microsoft answer on this subject is:
Currently this behavior is per design. However we will consider this
behavior improvement in a future release of reporting services The
only workaround at this point is to change the order of the
parameters.
Are the parameters on the RDL file set to visible, like below:
Just going to add this as an answer, because it solved the issue for me;
Delete the report on the server & deploy again.
What happens is that you completely remove the report and thus also its parameters. When you deploy a report its parameters their default values do not get overwritten in case it didn't have a default the first time you deployed.