Trying to upload a articulate 360 xapi published course into cornerstone LMS. As first step Published the course with basic settings reporting to LMS and tracking on passing the quiz at 80%.
At Content level there are 2 checkboxes in Cornerstone LMS (1.)IsScoring and (2. )Use TinCAn verbs for completion.
When unchecked both the course marks complete upon launch.
When Checked both or either the course does not mark complete upon passing the quiz.
In debug mode can see the statements generated with passed verb.. Please guide on this. How can I get the completion tracked. Am I missing some setting in Cornerstone LMS.
Related
I am a support Anaylst that works with a group of developers on ADO. I am having trouble changing the status or adding a task to an item without having to open the story or bug up in full then adding the progression or adding the task. Others on my team are able to do this by clicking on the dropdown within the box without the need to open. Same for the Tasks, in the To Do column there is a green plus where they click to add the task. I have to take the long route and create a child as a task and do this long form. It is quite time consuming. I have read on some posts online that this is becuase i have the Stakeholder role and that it needs to be basic in order for me to do this. Which would be great to try but my other teammates havethe stakeholder role as well and they are not having the same problem as I. I asked our ADO admin and he informed me that this is not a permissions issue and hinted that it could be a browser setting. I am using the latest version of Chrome but, this happens with Firefox and IE as well. I didn't try edge seeing outi it is powered by Chrome.
If anyone has any idea what this is and how I can fix this it would be awsome to go back to work and let them know what it was and what the fix is. They are all really busy, as am I, plus it's really not keeping me from doing my job...but if there is anything that I hate, it is wasting time and that's what I'm doing while taking several extra steps to do something.
adding a task to an item without
having to open the story or bug up in full then adding the progression
or adding the task.
For this issue, you need to check if Task is enabled in the Annotations of Settings .
having trouble changing the status , in the To Do column there is a green plus where they click to add the
task. I have to take the long route and create a child as a task and
do this long form.
For this issue, if the member is a stakeholder access level user，the New Items option will not be displayed. For details ,please refer to this official document.
This search produces zero results as you can see in the response body, but it is not triggering the zero results default dialog. I assume this means that if you create a custom results view, you must account for all possible scenarios of size = x?
This may require a deeper look at your capsule code since I am able to see a default "I couldn't find any [Concept]" without any issues.
I would recommend reaching out to the support team via the Contact Support option in the Help dropdown menu of Bixby Developer Studio so the team can look through your capsule code.
Problem
I have a simple Android app with 3 activities: Login, Browse_Catalog, and View_Item. On ChromeOS, I expected the Activities to stack in a single window. Instead, each Activity is appearing in its own, independently managed window on ChromeOS. Why is that happening? And how do I stop that behavior?
Request
My hope is that there is some configuration detail to keep activities stacked in a single window. I've tried looking for some flag in the Intent that launches the Activity, or some setting in the Manifest, but haven't found anything that indicates this behavior is intentional, or that there is a way to disable it.
Technical Details
ChromeOS 76.0.3809.102 (Official Build)(64-bit)
Asus Chromebox
Android Studio 3.4.2
targetSdkVersion: 28
minSdkVersion: 25
jvmTarget: 1.8
Observations
No error messages as far as I can tell. Just an awful user experience with multiple windows leading the user to think there are three separate programs running.
The Activities that should be hidden on the backstack, aren't very responsive, the windowmanager allows them to be resized briefly before reasserting a z-ordering on the activities.
The windowmanager does allow me to close an Activity/window from the backstack (e.g. Browse Catalog, while Viewing Item), but then backing off from the top Activity goes nowhere.
Possible Workarounds that are Unsatisfactory
I can kind-of workaround this by making the Activities launch in full-screen, but it feels like a huge kludge. It doesn't prevent users from minimizing or resizing individual windows.
Perhaps I could do this as single activity with multiple fragments, but I don't want to invest that much work, unless I absolutely have to.
For posterity: My mistake was the Browse_Catalog Activity had a line in the Manifest
<activity ...
android:launchMode="singleInstance"
/>
This creates the Activity as a single "Task", and won't launch any additional Activities into that Task. Here's a page with more details about Activities, Tasks, and BackStack
The default behavior (aka android:launchMode="standard") is what I was expecting, so removing this spurious setting solved the problem.
I am using the RandomProducts web part, and for some reason product options have no effect on the price even though I have added the price adjustments for each variant. Is this normal? I assumed this would work out of the box since its a default option but maybe I have to write my own code... just seems odd. Does something need to be enabled for product options to update the price of a product?
Are you sure you are not having an JS issues on your page? When using the Product Options, you define the option and any adjustment to the price. You then choose the products to apply the option to. When a user selects a specific option, there is a postback that occurs that updates the displayed price. If using the CartItemSelector web part, it will contain all of the postback JS needed to update the price within itself.
This works on a basic demo site so I suspect there is a JS issue that is causing the postback to not complete properly.
Another possible cause could be latency when posting the value back. If it is the first time you are running the site, it's possible the postback is taking longer than expected (due to recompilation) and it is appearing as if it's failing.
Other things to check:
On the Product Options General Tab
- Is "Enabled" checked?
- Is "Display price adjustments" checked?
I'd recommend to check the following things:
JavaScript errors via the developer tools of your browser
Caching settings/expiration for the web part or page
Enable SQL debug (Settings > System > Debug > Display on live site) and check which queries are executed to see where the price comes from
I have the following Message-level entry in my Error List from CodeContracts:
CodeContracts: Checked 410 assertions: 404 correct (6 masked)
I can't figure out:
What masked assertions are
How to locate the 6 that it mentions
Whether or not I should be concerned about them
Sorry for not posting code... I have no idea how to recreate this in a small sample :)
Many thanks
It's simple, in your project properties>Code Contracts>Static Checking> put the warning at "hi".
Now ccCheck made more warning.
Bye.
These seem to be assertions that are masked by virtue of their inclusion in the "baseline" file. From the documentation (emphasis mine):
6.6.8 Baseline
Bringing an existing code base to a point where the verier emits only a few warnings is dicult and time consuming, as it requires adding numerous contracts. To make it easier to use contracts on existing code bases, and to focus warnings introduced by new code or code changes, the Baseline functionality can be used.
To use the baseline functionality, check the box labelled Baseline and provide a file name to store the baseline in. The path is relative to the project output directory. When the analysis is run and the baseline file does not exist, the baseline is created. During this run, all warnings are shown in the output and stored in the baseline file as XML.
When the analysis is run and the baseline file exists, then the baseline acts as a filter and warnings already found in the baseline are not shown again. New warnings are shown and stored in a file called <baseline>.new, where <baseline> is the file name of the baseline file. Since the files are stored as textual XML, it is possible to edit them and to add additional failures to the baseline. The format does not depend on method ordering and additional XML tags for grouping can be introduced freely.
I was wondering about the "masked" messages, too; I turned off the "baseline" option, and they no longer appeared. The answer to your second question therefore seems to be "clear the 'baseline' check box."
As to whether you should be concerned about them, I would say, yes, you should.