I have a script which :
Loads an rtc workspace
Checks in a file to the workspace
The checked in file is not being reflected within 'pending changes'. Is there a hook I need to configure (or some other method)
so that any changes made using the scm tool are reflected on the rtc client ?
If you're using the RTC 4.0 Eclipse client on Windows, it might help to enable "Preferences > Team > Jazz Source Control > Local Changes > Automatically detect changes".
See "Rational Team Concert 4.0 "New and Noteworthy""
It will be reflect in the "Pending changes" view only if:
the local workspace has been loaded (attached to the repo workspace to which your script has checked in a file: it should be the same local workspace)
you refresh the "Pending changes" view, asking to refresh "Remotes and local changes", or to refresh directly the right local workspace)
(from "Using the RTC Eclipse client with other Tools")
From that thread, it seems the "Pending changes" view only refreshed automatically for remote changes:
The Pending Changes view should already refresh itself automatically when your Eclipse client receives RSS feed events reporting there are new incoming change sets.
Related
I have a functioning Google Sheets Add-on that is listed in the Google Workspace Marketplace. I've made changes in the new Apps Script Editor and tested them locally, now I want to push them to my users.
The process as I understand it, to press "New Deployment"
add a description and press "deploy"
after which I copy the "Deployment ID" into the Google Workspace Marketplace SDK page,
and hit SAVE in the bottom.
It's been a few hours and I still cannot see it being live.
Is there a review process for updates like this? Or am I missing a step?
The previous version is still being served to users as far as I can tell.
Update in response to the comment from #ziganotschka
I am making a Google Sheets Editor Addon, and I'm only now understanding the difference between that and the Google Workspace Addon. I've resubmitted my store listing for review with Google Workspace Addon disabled, and removed the "Common" part of my manifest. I've updated the "version" number to correspond to the latest deployment.
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon? And should updating the version number be sufficient to roll out an update?
From the question
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon?
It depends on what kind of test do you want to do, if your Apps Script project is bounded or a standalone project and what do you Editor add-on does and how it does that.
I.E. you might test a simple edit trigger (onEdit) by using a function for mocking the edit event object and passing it to the onEdit function. To be clear this doesn't need to create a new version and for testing and add-on it's not necessary to make a new deployment.
And should updating the version number be sufficient to roll out an update?
It depends on if the Cloud project OAuth consent screen was set for external use or for internal use, in the new version requires new scopes.
Let say that you fixed typo on a variable name, in this case only creating a new version and adding the version number to the add-on configuration page will be enough, but if you added a sensitive API and you add-on is set for external use, then you will have to update the OAuth consent screen and wait for Google review and approval.
I'm using Windows Server 2016 for Remote Desktop Services (RDS) the applications I've published are working fine. I've created a logon script so that my windows application starts when a user establishes RDS session. My problem is when a user logs in and my application runs automatically it doesn't show icon notification in system tray. I've gone through the below link and added the registry key which fixed the issue but it had also shown all unwanted application's icon as well.
https://social.technet.microsoft.com/Forums/lync/en-US/4122521f-7896-4098-a723-858077a243f1/remoteapp-notification-area-icons-not-visable?forum=winserverTS
Is there any way that I could programmatically dictate "rdpshell" to show only my application icon? or if there is any registry key specifically I could use for my application? or anything that I could use to show my application icon only?
Thanks.
I use Weblogic 12.1.3, when logged to admin server I see a tab with label "WLDF Console Extension" when choosing it, I get this message
"The WLDF Console Extension, which provided visual tools to display diagnostic information in this domain, has been replaced in this release by new integrated Monitoring Dashboard and Request Performance tools. For more information on these updates, please consult the online help and release notes for this release..."
How to hide this uselss tab, I have another installtion at work with the same version does not have this tab.
In general the WLDF extension is not installed by default so someone must have put it there and/or turned it on. To remove it there are 2 options:
Navigate to <domain dir>/console-ext and remove the diagnostics-console-extension.jar file. Restart your admin server.
Click the perferences link at the top of the admin console, click the Extensions tab, find the diagnostics-console-extension and disable it
If you ever need it back you can re-enable it or copy it back into your domain directory from the WL_HOME\server\lib\console-ext folder
We have already delivered the 1.0 version of our Worklight application. By mistake we have disabled the Direct update feature by updating the attribute "connectOnStartup = false"
We dont want to redeploy the application to markets (AppStore/GooglePlay) again, but wanted to make our users to utilize the direct update feature. We do have the access to WL server.
Our issue is little different from the one which is already discussed here "IBM Worklight - How to disable Direct Update?"
How can we provide the direct update feature to our end users without redeploying the application to AppStore/Googleplay. And just by changing the Webresources of the application.
We are using the adapters in our application but no where we are explicitly calling the "WL.Client.connect".
The Direct Update feature is always enabled by default.
You need to edit your question and explain what it is you've done in your Worklight project.
The feature will not work if:
You have set connectOnStartup:false
You are not using WL.Client.connect
You are not invoking adapters
You disabled it via the checkbox in Worklight Console
Otherwise, the feature will work, and a check for Direct Update will be performed:
On application startup
On return to foreground
The application will need Re-deployment on the App stores.
So the solution to your problem is
Rebuild the Application with connectOnStartup:true.
Redeploy the Application on App Stores
Once the users download the updated application, future updates will go to the users directly.
While rebuilding, make sure that you change the Version of your application within ApplicationDescriptor.
I have used an Android device (Samsung Galaxy S3 Android version 4.1.1) to view the App Info of my hybrid app. The "Application" size is around 10MB and the "Data" size is around 1MB. After that, I clicked "Clear data" button so that the "Data" size became 0MB and "Application" size remained the same.
When I launch the app again, the direct update box comes out although there is no new app release (No second build has been done). Is it an expected behavior?
Worklight version: 5.0.6
Steps:
1. Deploy an app to Worklight Server and install it in the device
2. Update the HTML file and make a build
3. At this moment, the device shows the direct update dialog. Update the app to latest version.
4. Click "Clear data" in App Info
5. Launch the app again. It shows the direct update dialog again although there is no second build occurs after "Clear data" was done
Thanks!
Based on your edit with the steps you have taken, yes, this is expected.
When installing an application on a device a chucksum is generated for it in both the client and server. After triggering a Direct Update this checksum value changes and remembered. After clearing the data, you basically return the application to its previous checksum and thus when the app is re-launched (or brought to the foreground from the background), the server detects that the value in the server differs from that in the client, and sends a Direct Update request.