We've recently moved off Netsuite as our main CRM, and I've been tasked with disabling it. We still have historic tickets in there that need closing, but I want to disable Netsuite from picking up any new tickets from our support mailbox.
I'm new in this role and have little Netsuite experience. Can anyone tell me how to prevent Netsuite from picking up new support tickets, while allowing us to work on closing the existing tickets? Our new CRM is picking up the new tickets.
I've been googling, but can't find out how to do this. I'm very new to Netsuite, and as soon as I've worked out how to perform the basic admin functions, we're moving away from it. I'm cautious that I need to still allow open tickets to be processed and worked on, so can't just cancel everything down.
Can anyone point me in the correct direction?
Thanks in advance!
There is indeed a forwarder on our support address, forwarding to a unique looking Netsuite address. I've disabled the forward, and also unchecked the Email Case Capture box. This allows us to continue working on already created cases, whilst preventing Netsuite from creating new cases. Problem solved, thanks again Jdg50!
Cases in Netsuite are created either through a form or email capture via forwarding a company address to a Netsuite address.
The Email Case Capture feature at Setup > Company > Enable Features > CRM > Support automatically
converts customer support messages your company receives into organized cases in NetSuite.
Depending on the specific requirements of your business, you can use case capture to create a simple
catch-all support address, or you can create a more sophisticated customer support model by using
Case Profiles.
From: https://docs.oracle.com/cloud/latest/netsuitecs_gs/NSSMG/NSSMG.pdf
Case capture works by forwarding your company’s support email address to a NetSuite-generated
address. You will need to make a note of this when setting up forwarding on your mail server.
Logic dictates that removing/unchecking case capture in this setting will turn off case creation. You may also need to turn off the case forwarding/capture user setup in your exchange, depending on how it was originally setup.
This won't erase existing cases, but it will stop new cases from being created.
Related
An existing bill has an approval record, due to normal approval map. With the help of SQL, I updated the value EPApproval.ownerID, and assigned a new approver. Next, I logged in as the user who is associated with the updated owner ID. Finally I can Approve the bill. I wanted to see if it's possible to achieve the same success via ACM Framework. The client has some cases in which an employee delegate must be assigned as the document approver. Currently it isn't possible to edit the approval record via UI.
Probably you are aware of this, but in Acumatica it is possible to approve the following documents:
Those assigned to you.
Those assigned to other users of your workgroup.
Escalated documents assigned to users of workgroups that are at lower levels in the company tree but in the node of your workgroup.
Refer to https://help-2018r1.acumatica.com/(W(2))/Wiki/ShowWiki.aspx?pageid=1fe1afcc-e676-466e-8c3f-cbf64857e32a
Therefore, it might be possible to achieve what you need through the use of workgroups and proper configuration of the Organization Chart.
Unfortunately, Acumatica does not have delegate functionality. You might consider upvoting this entry on the Acumatica Ideas site (as it has already been raised previously): https://feedback.acumatica.com/ideas/ACU-I-2162
Regarding your question on whether it is possible to change the Approver, you should be able to develop this as a Customization. For example you could consider doing a Custom screen (or perhaps customize an existing screen) from where you can add this functionality. You can consider using PXDatabase.Update as well to update the entry (although this shouldn't be used in case you are doing a solution which is to be ISV certified)
I have one G Suite account with three domains (mainly many emails).
Now I would like to separate one domain to other fresh G Suite account. Of course with historical emails.
Anybody know how to do this? It's possible without G Suite support team?
There are different ways of doing this and yes, you can do it yourself. Please consider that it can be tricky depending on the amount of data you want to move.
The main steps are:
Create a new account with a temporary domain (the same domain can not be in two consoles at the same time)
Migrate all the contents from your current account to the new one. You have different options to do this. The cheapest one is the Data Migration Service (DMS) that will only allow you to migrate only email using the IMAP protocol (so you need to know the users' passwords). Google support for the DMS is best effort, so if you have time and budget I recommend to use a commercial tool (my tool of choice here is Cloud Migrator) that is also able to migrate calendar items and Google Drive files using the Google APIs (so it is transparent for the users).
In a cut-off date that you agree with your users you remove the domain from the original console, you add it to the new one and perform a mass rename (my tool of choice here is GAM).
There are many variables that can make the process much more complex that are difficult to describe in a single answer and this kind of activities usually require a dedicated project and a (small) team: I really suggest you to get some help.
A word of warning:
I did this on Bluehost (transferring G Suite ownership of a domain from one Bluehost account to another) through Bluehost customer support.
It took 3 separate calls to Bluehost to get everything fully moved over. Make sure that your hosting provider sends you an email confirmation that everything happened successfully, because as a reseller of a Google product, they may not have complete authority over transferring ownership of Google's product.
Best regards.
Also in reference to the domain go to Google Domain and you can see all the options you have in reference to your domain website etc. It is very self-explanatory.
wc.
I develop web applications, which use a number of third party applications/code/services.
As part of the job, we regularly check with the Full Disclosure mailing list http://seclists.org/fulldisclosure/ for any of the products we use.
This is a slow process to do manually and subscribing to the list would cost even more time, as most reports do not concern us.
Since I can't be the only one trying to keep up with any possible problems in the code I use, others have surely encountered (and hopefully solved) this problem before.
What is the best way to monitor the Full Disclosure mailing list for specific products only?
Two generic ways to do the same thing... I'm not aware of any specific open solutions to do this, but it'd be rather trivial to do.
You could write a daily or weekly cron/jenkins job to scrape the previous time period's email from the archive looking for your keyworkds/combinations. Sending a batch digest with what it finds, if anything.
But personally, I'd Setup a specific email account to subscribe to the various security lists you're interested in. Add a simple automated script to parse the new emails for various keywords or combinations of keywords, when it finds a match forward that email on to you/your team. Just be sure to keep the keywords list updated with new products you're using.
You could even do this with a gmail account and custom rules, which is what I currently do, but I have setup an internal inbox in the past with a simple python script to forward emails that were of interest.
Many unwanted users are creating fake accounts on our website to pester us.
What can we do?
Add a captcha to keep out robots, then monitor IP addresses for multiple create attempts and block the ones that make more than 1 or 2 (depending on nature of site).
If you give us your web service software name (IIS, glassfish, tomcat, etc...) there may be some more specific addons that could help you.
You can require all new accounts to be manually accepted by an admin before they're activated. Checking the IP's for multiples is okay, but ineffective if they're using proxies.
Generally, you just have to make it enough of a pain so that they get bored and move on.
Most of the websites do these things to prevent that.
Create an email verification while registering.
Add Captcha to register form.
Do not accept emails from temporary/disposable email services.
Monitor IP addresses and block them from creating multiple accounts.
I'm pretty new to sharepoint-development, so I thought I'd check real quick with the gurus in here.
I've been given the task of building a replacement for the built-in Alert Me feature. The main reason for this is to allow for alerting members of a role with a forms authenticated sharepoint.
This is where you guys come in. I know you can build an immediate Alert Me function by creating list item event receivers.
However, if I wanted to create the summary-feature (daily/weekly notifications) - what would be the best way to go about this?
With very limited knowledge, all I could think of was to create a Windows Service, which checks daily for changes to the lists, and sends notifications accordingly, in one summarized email.
Would I be wrong to assume that this is, if not the best/only way to do it, at least one way of doing it?
And could I use the SPChangeCollection to accumulate the changes?
thanks in advance :)
Don't create windows service: you have SharePoint job for scheduled tasks.
However, I would reconsider the need. SharePoint alerts already offer immediate/daily/weekly alerts. thos member of the role (group?) can perfectly choose the "Alert me" individually. i personnaly would consider otherwise as spam (how do you unsubscribe, then?)