We are trying to implement Push Notification to Webhook, for our initial testing we used Opportunities screen. When we update any record or create new opportunities nothing is being pushed to webhook and in request profiler we observed the RowCount as 0. As per Acumatica guide lines we are not using any formulas and complex joins in GI. This is standard Acumatica GI we used in Push Notifications.
When we initially verified this it was not working, so we thought it may be because of our customizations package, so we unpublished all our package and tested again but still not working.
We are on Acumatica 2019R1 Build - 19.106.0020 (without any customization packages published). How can we fix this?
Here are some screenshots:
I have created a new webhook for CROpportunites with simple GI and it is working for me.
In, Generic Inquiry I have added Estimation Date(CloseDate DB filed), when this field is modified, then the details will be triggered. Please find the screenshots for reference.
Please let me know if you still have any questions.
Opportunites Screen
Push Notifications screen
CR Opportunites GI
Details we can see on Webhook Site
Related
is it possible to collaborate online with TFS? I mean, when I move a task, others can see it in real time without sharing screen or updating the page. Thank you!
Azure DevOps Server 2020 Update 1 RC1 and higher has live updates on work items. If you change a work item someone else has open in view mode, it will update in their client.
Alternatively
You can enable notifications using ../DefaultCollection/_usersSettings/notifications
You can use the Follow icon to follow a work item. Any changes will result in an e-mail to you saying the item has changed, and what has changed.
If you move a story out of an iteration, the Taskboard (../_sprints/taskboard/..) view updates automatically for all users viewing that iteration
Similarly, if you add/edit/move/change state on a task in an iteration the Taskboard will update.
I look for a way to collect and save activity and security logs from the Azure devops server(onprem 2019.1).
Logs include - user logins, build events, work item events, security changes etc.
I'm aware about this option https://server_name/tfs/_oi/_diagnostics/activityLog. But it's not an api interface.
Any Idea how it's can be implemented that?
Thanks.
TFS keeps track of an activity log of all recent activities. This information is stored in 2 tables inside Tfs_Configuration and Tfs_collectionname called tbl_Command and tbl_Parameter. These tables keep a record of every single command that every single user has executed against TFS for the last 14 days.
If you don’t want to get activity log through tbl_Command table and hidden activity log page (http://server:port/tfs/_oi), I’m afraid there is no other way at present.
You could add your request for this feature on our UserVoice site, which is our main forum for product suggestions. After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it.
The current documentation does not match the new interfaces exactly but what I have being able to put together is displayed in the screenshots below.
What does work is:
When I push a comment to GitLab a link is built and links to the properly referenced JIRA ticket.
JIRA is added as a LHS menu item which opens link I define as Web URL (see below).
What does not work is:
The JIRA ticket does not display the comment.
On GitLab
My settings keep failing the integration test and I have no idea what the problem is.
myproject > Settings > Integrations
On JIRA CLOUD
I have created a user as per instructions in the docs
https://gitlab.com/help/user/project/integrations/jira
https://gitlab.com/gitlab-org/gitlab-ce/blob/8-13-stable/doc/project_services/jira.md
From what I can gather is if I want to comment I just have to mention a correctly formatted JIRA ticket ID and if I want to change the state of a ticket I need to set the correct Transition ID(s) which I can find in my JIRA workflow.
I am able to log in manually to JIRA with the "Gitlab Dev" user account, and post comments.
Has anyone else got this to work with the newer admin layouts?
Make sure that the Jira user you set up for the integration has the correct access permission to post comments on a Jira issue and also to transition the issue, if you’d like GitLab to also be able to do so.
Jira issue references and update comments will not work if the GitLab issue tracker is disabled.
I am managing a projects (subtype of Activity) collection and I would like to implement a simple "Status change" log.
The idea would be that of replicating the simple but effective order management log seen in Prestashop (see image), Order management screen: User selects the new project status, clicks [UPDATE STATUS], and a new row gets appended to the log with new status, date of the change, person having triggered the change.
The basic implementation could be a text area used as a log, the best implementation possible would be that of having a grid.
Could somebody point me in the right direction to do this?
I am using version 2011 but moving to 2015 in a few days.
I suggest using auditing:
The following list identifies the data and operations that can be audited:
Create, update, and delete operations on records.
You could have an OptionSet representing the status of a project. If you enable auditing on this field (and enable auditing in general for CRM) you will be able to see an audit history of changes to the field. To do so users will have to navigate to the Audit History of the record.
The audit history will look similar to the following (in 2011):
If you don't want to use Auditing as suggested by Henrik in his answer, the alternative is to create a custom entity that will act as a log entity for your status change.
In order to implement the track of the changes, you need to implement a Plugin that will be triggered on the update message and will create the records inside the new custom entity.
The SharePoint install is a SP2010 install on a 2008 R2 server. Everything is fully patched. I am running the SP Designer on the SharePoint Server directly.
I have a workflow which is intended to send an email when a new document is created in a custom list. I have deliberately kept the workflow very simple in order to illustrate this problem.
After creating this single step workflow in SP Designer, I click "Check for Errors" and SP Designer reports "The workflow contains no errors".
I then click "Publish" but the Workflow Error dialog is displayed with the message
Errors were found when compiling the workflow. The workflow files
were saved but cannot be run.
Clicking the advanced button reveals more information:
Could not publish the workflow because the workflow configuration file
contains errors
Any suggestions gratefully received
I'll share what fixed it for me - deactivating all workflow features at the site collection level (that is, Workflows, Three-state workflow, Publishing Approval Workflow) and then reactivating the features. I was then able to publish my workflow. This post helped, not sure whether this only works for 365 though, but it's sure worth trying first if you are considering a reinstall.
after googling for quite some time, i think it's an authentication issue. How is your SharePoint set up? Do you use HTTPS for authentication? If so check out this article.
I know this error message from sharepoint. I got this by dealing with multiple lookup fields refering to other lists. Even when I check the worfklow for errors SharePoint says that its all fine but i can't publish it at all.
Try to build a new Test-Site on your Site Collection. Build a Custom Document Library, leave it standard and then set up a new simple workflow just sending a mail.
Fill out the needed fields in mail only using simple values. Send to your mailadress, simple mail subject and simple mail body.
Set the workflow to run only manually.
Try to publish the workflow.
When this is working, then compair to your existing workflow and change your values by trail and error.
After doing a clean install of the OS and SharePoint, workflows are working flawlessly. I can only conclude that the problems were caused by left over registry settings from MOSS 2007. Thanks for the suggestions that people made.
This could also happens if you chage the URL of the web application, all you have do is click the Design button from the library itself.
when changinf the URL from http://server/Site to example: http://server.xx1.net/site, and you try to publish it tries the old url.
what helped in my situation is changing from start workflow automatically to manually.some times answers for critical situation is very easy. hope it helps, many thanks
I ran into this problem and after digging for days and folks suggesting to rebuild the servers, disabling and re-enabling site features, remove previous workflow versions, etc. and trying everything except rebuilding the servers (not practical for clients production environment). I decided to try some tests and found that this issue was only happening on one particular list no matter how simple or complex the workflow was... And when I would check the box for start automatically on item create (or when item changed) it would fail to publish and give the error above, but if I published it with just manually start worked fine. Finally after deleting views and some more testing, I discovered that there was over 240+ columns in this list (I did not create it...) and 50+ workflows set to run on create... Thankfully I have a test environment I built out for the client so I sync'd the Site Collection database back to test environment from Production re-ran my tests and got same error... So what resolved the problem and what was the ultimate cause of the problem, there was to many columns defined in the list and I had to delete several columns to publish the workflow in the test environment. This actually issue translates into the there is a limit in SQL Server on how much data the list can store each type of column takes up so much space read more about it here:
https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Column
So what I did in production was worked with my client to determine how to break up the list into multiple lists and have relationships between them, thus moving some of the columns and data to another list (Think database/list normalization)... I hope this solution helps someone.